From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Дмитрий Иванов <firstdismay(at)gmail(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Difference in execution plans pg12 vs pg14 |
Date: | 2021-12-11 01:13:28 |
Message-ID: | ae373a95-c25f-596b-f525-1905687ac9e4@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Дмитрий Иванов | 2021-12-11 01:51:55 | Re: Difference in execution plans pg12 vs pg14 |
Previous Message | Дмитрий Иванов | 2021-12-11 01:00:40 | Difference in execution plans pg12 vs pg14 |