pg.ddx.io pgsql-docs@postgresql.org mailing list archive
help / color / mirror / Atom feedROWS vs RANGE in release notes for pg 16
2+ messages / 2 participants
[nested] [flat]
* ROWS vs RANGE in release notes for pg 16
@ 2023-08-18 23:41 Erwin Brandstetter <brsaweda@gmail.com>
2023-08-19 01:03 ` Re: ROWS vs RANGE in release notes for pg 16 Jonathan S. Katz <jkatz@postgresql.org>
0 siblings, 1 reply; 2+ messages in thread
From: Erwin Brandstetter @ 2023-08-18 23:41 UTC (permalink / raw)
To: pgsql-docs
The release notes for Postgres 16 says here:
https://www.postgresql.org/docs/16/release-16.html#RELEASE-16-PERFORMANCE
> Allow window functions to use ROWS mode internally when RANGE mode is
specified but unnecessary (David Rowley)
But the fix also applies to the much more common case where no mode has
been specified, RANGE unfortunately being the default - including the most
common use case "row_number() OVER (ORDER BY col)". This is what made me
investigate, test and eventually propose a fix in the first place. See:
https://www.postgresql.org/message-id/flat/CAGHENJ7LBBszxS%2BSkWWFVnBmOT2oVsBhDMB1DFrgerCeYa_DyA%40m...
https://www.postgresql.org/message-id/flat/CAApHDvohAKEtTXxq7Pc-ic2dKT8oZfbRKeEJP64M0B6%2BS88z%2BA%4...
Also, I was hoping to get a mention in the release note for working this
out:
> Allow window functions to use the faster ROWS mode internally when RANGE
mode is specified or would be used by default, but unnecessary (David
Rowley, Erwin Brandstetter)
Regards
Erwin
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: ROWS vs RANGE in release notes for pg 16
2023-08-18 23:41 ROWS vs RANGE in release notes for pg 16 Erwin Brandstetter <brsaweda@gmail.com>
@ 2023-08-19 01:03 ` Jonathan S. Katz <jkatz@postgresql.org>
0 siblings, 0 replies; 2+ messages in thread
From: Jonathan S. Katz @ 2023-08-19 01:03 UTC (permalink / raw)
To: Erwin Brandstetter <brsaweda@gmail.com>; pgsql-docs
Hi Erwin,
On 8/18/23 7:41 PM, Erwin Brandstetter wrote:
> The release notes for Postgres 16 says here:
> https://www.postgresql.org/docs/16/release-16.html#RELEASE-16-PERFORMANCE <https://www.postgresql.org/docs/16/release-16.html#RELEASE-16-PERFORMANCE;
>
> > Allow window functions to use ROWS mode internally when RANGE mode is
> specified but unnecessary (David Rowley)
>
> But the fix also applies to the much more common case where no mode has
> been specified, RANGE unfortunately being the default - including the
> most common use case "row_number() OVER (ORDER BY col)". This is what
> made me investigate, test and eventually propose a fix in the first
> place. See:
>
> https://www.postgresql.org/message-id/flat/CAGHENJ7LBBszxS%2BSkWWFVnBmOT2oVsBhDMB1DFrgerCeYa_DyA%40m... <https://www.postgresql.org/message-id/flat/CAGHENJ7LBBszxS%2BSkWWFVnBmOT2oVsBhDMB1DFrgerCeYa_DyA%40m...;
> https://www.postgresql.org/message-id/flat/CAApHDvohAKEtTXxq7Pc-ic2dKT8oZfbRKeEJP64M0B6%2BS88z%2BA%4... <https://www.postgresql.org/message-id/flat/CAApHDvohAKEtTXxq7Pc-ic2dKT8oZfbRKeEJP64M0B6%2BS88z%2BA%4...;
>
> Also, I was hoping to get a mention in the release note for working this
> out:
>
> > Allow window functions to use the faster ROWS mode internally when
> RANGE mode is specified or would be used by default, but unnecessary
> (David Rowley, Erwin Brandstetter)
Thanks for flagging. I suggest adding the comment to the release notes
thread on -hackers:
https://www.postgresql.org/message-id/flat/ZGaPa7M3gc2THeDJ%40momjian.us
Jonathan
Attachments:
[application/pgp-signature] OpenPGP_signature (839B, ../../9272ffff-3cdb-ebe4-4f4a-a89ea2081be0@postgresql.org/2-OpenPGP_signature)
download
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2023-08-19 01:03 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2023-08-18 23:41 ROWS vs RANGE in release notes for pg 16 Erwin Brandstetter <brsaweda@gmail.com>
2023-08-19 01:03 ` Jonathan S. Katz <jkatz@postgresql.org>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox