on Fri, 15 Sept 2023 at 0:00, Adrian Klaver wrote:
> Why not just run ANALYZE on the new 14.7 instance?
The statistics were manually updated to fix the access plan.
I was trying to see if I could fix the access plan in a similar way in 9.2 ->
14.7.
I probably will run ANALYZE soon because I hav
on Thu, 14 Sept 2023 at 23:43, David Rowley wrote:
> This likely is due to the query planner not giving any preference to the
> index that allows more quals to go into the index condition. Once the
> selectivity estimate gets as low as 1 row then the costs between each index
> don't vary very
Hi all
I am planning to migrate from PostgreSQL9.2 to PostgreSQL14.7.
Running the same SQL with the same statistics as previous versions resulted in
different access plans.
I have no knowledge of the PostgreSQL planner and would like to be informed.
Please assist.
Behavior:
I am using an envi
Thank you for your comments. Sorry for the late reply.
From: Kirk Wolak Sent: Friday, November 25, 2022 6:12 PM
> My first question is why are you not using "WHERE CURRENT OF" cursor_name?
I thought that cursors are preferred for manipulating large numbers of rows.
So I did not consider using
Hi All.
When multiple sessions tried to acquire a row lock on the same tuple
sequentially, I expected
that the first session waiting for the lock would acquire the lock first
(FIFO). However, when we
actually tested it, there were cases where a session that was behind a first
session acquired
a
