MIME-Version: 1.0
References: 
 <CABeG9LsZ2ozUMcqtqWu_-GiFKB17ih3p8wBHXcpfnHqhCnsc7A@mail.gmail.com>
 <1c6fa18692a77ff6098dedc0c150df24ffe9db89.camel@cybertec.at>
In-Reply-To: <1c6fa18692a77ff6098dedc0c150df24ffe9db89.camel@cybertec.at>
From: Masahiko Sawada <sawada.mshk@gmail.com>
Date: Wed, 2 Jun 2021 18:16:08 +0900
Message-ID: 
 <CAD21AoAv5gdFEggmHj-GeSVvkZkhv1fvLf3xe8aPUS7y8tOTNg@mail.gmail.com>
Subject: Re: Update maintenance_work_mem/autovacuum_work_mem to reflect the
 1GB limitation with VACUUM
To: Laurenz Albe <laurenz.albe@cybertec.at>
Cc: =?UTF-8?B?TWFydMOtbiBNYXJxdcOpcw==?= <martin.marques@gmail.com>,
	pgsql-docs@lists.postgresql.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: 
 <https://www.postgresql.org/message-id/CAD21AoAv5gdFEggmHj-GeSVvkZkhv1fvLf3xe8aPUS7y8tOTNg%40mail.gmail.com>
Precedence: bulk

On Wed, May 5, 2021 at 7:03 PM Laurenz Albe <laurenz.albe@cybertec.at> wrot=
e:
>
> On Mon, 2021-05-03 at 13:48 -0300, Mart=C3=ADn Marqu=C3=A9s wrote:
> > We should add a line that indicates that there is a limitation (that
> > should be IMO, backported to documentation of earlier versions as it
> > affects all supported versions), at least until such limitation is
> > lifted.
>
> Here is a patch for that,

The patch adds the description in the autovacuum_work_mem section.
Isn't it better to add it in mantenance_work section or VACUUM command
section since this limitation is not only for autovacuum?

Regards,

--=20
Masahiko Sawada
EDB:  https://www.enterprisedb.com/