On Wed, Sep 27, 2023 at 02:05:44AM +1300, David Rowley wrote: > On Tue, 12 Sept 2023 at 03:03, Bruce Momjian <br...@momjian.us> wrote: > > > > On Mon, Sep 11, 2023 at 10:02:55PM +1200, David Rowley wrote: > > > It's certainly not a show-stopper. I do believe the patch makes some > > > improvements. The reason I'd prefer to see either "and" or "and/or" > > > in place of "or" is because the text is trying to imply that many of > > > these operations can run at the same time. I'm struggling to > > > understand why, given that there could be many sorts and many hashes > > > going on at once that we'd claim it could only be one *or* the other. > > > If we have 12 sorts and 4 hashes then that's not "several sort or hash > > > operations", it's "several sort and hash operations". Of course, it > > > could just be sorts or just hashes, so "and/or" works fine for that. > > > > Yes, I see your point and went with "and", updated patch attached. > > Looks good to me.
Patch applied back to Postgres 11. -- Bruce Momjian <br...@momjian.us> https://momjian.us EDB https://enterprisedb.com Only you can decide what is important to you.