Re: Query ID Calculation Fix for DISTINCT / ORDER BY and LIMIT / OFFSET
Sami Imseih <samimseih@gmail.com>
From: Sami Imseih <samimseih@gmail.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: David Rowley <dgrowleyml@gmail.com>, Bykov Ivan <i.bykov@modernsys.ru>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2025-03-11T22:35:10Z
Lists: pgsql-hackers
> and simple. However, Sami seems to have concerns about the overhead of > doing this. Is that warranted at all? Potentially, there could be a > decent number of NULL fields. It'll probably be much cheaper than the > offsetof idea I came up with. I have not benchmarked the overhead, so maybe there is not much to be concerned about. However, it just seems to me that tracking the extra data for all cases just to only deal with corner cases does not seem like the correct approach. This is what makes variant A the most attractive approach. -- Sami
Commits
-
Optimize Query jumble
- ad9a23bc4f51 18.0 landed