From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | David Rowley <dgrowleyml(at)gmail(dot)com> |
Cc: | Melanie Plageman <melanieplageman(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: First draft of PG 17 release notes |
Date: | 2024-05-20 00:12:31 |
Message-ID: | ZkqVby4Dh8-FO-0_@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sun, May 19, 2024 at 03:53:38PM +1200, David Rowley wrote:
> On Sun, 19 May 2024 at 02:40, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> >
> > On Thu, May 16, 2024 at 03:35:17PM +1200, David Rowley wrote:
> > > "Additionally, vacuum no longer silently imposes a 1GB tuple reference
> > > limit even when maintenance_work_mem or autovacuum_work_mem are set to
> > > higher values"
>
> > Slightly adjusted wording patch attached and applied.
>
> Thanks for adjusting.
>
> It's a minor detail, but I'll mention it because you went to the
> effort to adjust it away from what I'd written...
True.
> I didn't make a random choice to use "or" between the two GUCs.
> Changing it to "and", IMO, isn't an improvement. Using "and" implies
> that the silent limited was only imposed when both of these GUCs were
> set >= 1GB. That's not true. For the case we're talking about here, if
> autovacuum_work_mem is set to anything apart from -1 then the value of
> maintenance_work_mem does not matter.
Okay, changed to "or".
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2024-05-20 00:20:52 | Re: commitfest.postgresql.org is no longer fit for purpose |
Previous Message | jian he | 2024-05-20 00:00:00 | Re: </replaceable> in parentesis is not usual on DOCs |