Re: Query ID Calculation Fix for DISTINCT / ORDER BY and LIMIT / OFFSET - Mailing list pgsql-hackers

From David Rowley
Subject Re: Query ID Calculation Fix for DISTINCT / ORDER BY and LIMIT / OFFSET
Date
Msg-id CAApHDvrhM=ZZRgMkf7YFhHZbn+Vm4iL+BWB0U8kTA1ryCuH65A@mail.gmail.com
Whole thread Raw
In response to Re: Query ID Calculation Fix for DISTINCT / ORDER BY and LIMIT / OFFSET  (Michael Paquier <michael@paquier.xyz>)
Responses Re: Query ID Calculation Fix for DISTINCT / ORDER BY and LIMIT / OFFSET
List pgsql-hackers
On Mon, 24 Mar 2025 at 15:23, Michael Paquier <michael@paquier.xyz> wrote:
> And here we get 18564.06 (head) vs 16667.92 (patch) so a 10.7%
> difference in this run.  Hence the automatic addition of NULL to the
> jumbling is disappointing here, even if this is what I'd see this as a
> worst case scenario, unlikely what one would see for real if they care
> about monitoring.

Can you share which patch you tested here?  There are many patches on
this thread and I don't want to make assumptions about which one these
are the results for.

It sounds like it wasn't your latest patch as you mentioned "automatic
addition of NULL to the jumbling".  That doesn't sound like the
correct description for your latest patch.

David



pgsql-hackers by date:

Previous
From: David Rowley
Date:
Subject: Re: Patch: Cover POSITION(bytea,bytea) with tests
Next
From: Tender Wang
Date:
Subject: Re: Add mention in docs about locking all partitions for generic plans