Yes, I did.
Step1
sudo /usr/lib/postgresql/14/bin/pg_dump --file "/home/dismay/uchet/Uchet.backup" --host "server" --port "5999" --username "back" --no-password --verbose --format=c --quote-all-identifiers --blobs --disable-triggers --encoding="UTF8" "Uchet"
Step2
Manual DROP/CREATE BASE from template 0 (We have to do this because of the difference in locales Win EDB 'Russian_Russia.1251' <> Debian 'ru_RU.UTF-8')
Step3
sudo /usr/lib/postgresql/14/bin/pg_restore --host "127.0.0.1" --port "5998" --username "back" --no-password --dbname "Uchet" --disable-triggers --format=c --verbose "/home/dismay/uchet/Uchet.backup" 2> "/home/dismay/uchet/uchet_all.log"
--
Regards, Dmitry!
сб, 11 дек. 2021 г. в 06:59, Adrian Klaver <adrian.klaver@xxxxxxxxxxx>:
On 12/10/21 17:51, Дмитрий Иванов wrote:
> Yes, I did.
> I reset table statistics, did (VACUUM) ANALYZE, recreated index. Nothing
> changes.
> I've deleted the database many times, dozens of times. Maybe something
> is broken?
How did you do the upgrade?
> --
> Regards, Dmitry!
>
>
> сб, 11 дек. 2021 г. в 06:13, Adrian Klaver <adrian.klaver@xxxxxxxxxxx
> <mailto:adrian.klaver@xxxxxxxxxxx>>:
>
> On 12/10/21 17:00, Дмитрий Иванов wrote:
> > Afternoon. I was able to make the necessary changes to my base
> needed to
> > migrate win_pg12 to debian pg14.
> > But there is a new problem, which was not there at the initial
> stage so
> > I checked:
> >
> > win_pg12:
> > -> Index Scan using index_class_tree_full on class c
> (cost=0.28..2.50
> > rows=1 width=235) (actual time=0.030..0.032 rows=1 loops=1)
> > Index Cond: (id = 650)
> > debian_pg14:
> > -> Index Scan using index_class_tree_full on class c
> (cost=0.28..2.50
> > rows=1 width=235) (actual time=842.795..842.796 rows=1 loops=1)
> > Index Cond: (id = 650)
> >
> > I'm wondering where to dig next...
>
> Did you run ANALYZE(updates table stats) on the 14 instance after doing
> the upgrade?
>
> > --
> > Best regards, Dmitry!
>
>
> --
> Adrian Klaver
> adrian.klaver@xxxxxxxxxxx <mailto:adrian.klaver@xxxxxxxxxxx>
>
--
Adrian Klaver
adrian.klaver@xxxxxxxxxxx