Re: Use generation context to speed up tuplesorts - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: Use generation context to speed up tuplesorts
Date
Msg-id CAH2-Wz=n_BHUeWwOOQEF3wqVZD_iBuQG+b+4F77zsijrbnZ+_w@mail.gmail.com
Whole thread Raw
In response to Re: Use generation context to speed up tuplesorts  (Noah Misch <noah@leadboat.com>)
List pgsql-hackers
On Sat, Apr 23, 2022 at 5:59 PM Noah Misch <noah@leadboat.com> wrote:
> This (commit 77bae39) did not change function parameter counts, and
> TUPLESORT_RANDOMACCESS generally has same the same numeric value as "true".  I
> get no warning if I pass "true" for the "sortopt" flags parameter.  Hence, I
> suspect this did not break the API.  Should we be happy about that?  I'm fine
> with it.

If I happened to believe that this issue (or one like it) might have
real negative consequences, and that those consequences could easily
be avoided (by making the API break impossible to overlook), then I
would object -- why even take a small chance? Fortunately I don't
believe that we're even taking a small chance here, all things
considered. And so I agree; this issue isn't a concern.

-- 
Peter Geoghegan



pgsql-hackers by date:

Previous
From: Noah Misch
Date:
Subject: Re: Use generation context to speed up tuplesorts
Next
From: Isaac Morland
Date:
Subject: Re: Why is EXECUTE granted to PUBLIC for all routines?