Request a Demo
Home   >   mailing lists

Re: Possible regression in PG18 beta1 - Mailing list pgsql-hackers

From Sadeq Dousti
Subject Re: Possible regression in PG18 beta1
Date
Msg-id CADE6LvjBOrFObDOGBayzcLfWRScN6hHQopPjj5R_hSeJXOjauw@mail.gmail.com
Whole thread Raw
In response to Re: Possible regression in PG18 beta1  (Sami Imseih <samimseih@gmail.com>)
List pgsql-hackers
Tree view
thanks. I don't see regression for a normal table, at least for this test.

No, there isn't. I just added them as per your request ;) 


In terms of your original test, I tried it out on my Ubuntu machine
and with your test as-is, I see 2.8 seconds on 17.5 and 3.3 seconds
on HEAD if the plan performs a seq scan without parallelism.

Which is unexpected, no? 


However, the test as you have it is indexing all columns
on the table. If I just index on the filtered column

Yes, I agree. Changing the indexing setup will diminish the difference. However, given the sub-optimal index, PG18 seems to be slower.

Also, there's a meaningful difference in the plans for TEMP table vs. UNLOGGED, which is interesting.

Best regards, 
Sadeq Dousti 

pgsql-hackers by date:

Previous
From: Sami Imseih
Date:
Subject: Re: Possible regression in PG18 beta1
Next
From: Masahiko Sawada
Date:
Subject: Re: POC: enable logical decoding when wal_level = 'replica' without a server restart