Re: Correct the documentation for work_mem - Mailing list pgsql-hackers

From David Rowley
Subject Re: Correct the documentation for work_mem
Date
Msg-id CAApHDvrJxauZ6BC3=2JTDE-CUXbMTVLjV2S3gw-=bFRdRAgfsA@mail.gmail.com
Whole thread Raw
In response to Re: Correct the documentation for work_mem  (Bruce Momjian <bruce@momjian.us>)
Responses Re: Correct the documentation for work_mem
List pgsql-hackers
On Tue, 12 Sept 2023 at 03:03, Bruce Momjian <bruce@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.

David



pgsql-hackers by date:

Previous
From: Nishant Sharma
Date:
Subject: [Code Cleanup] : Small code cleanup in twophase.sql
Next
From: Amit Langote
Date:
Subject: Re: generic plans and "initial" pruning