Re: Update maintenance_work_mem/autovacuum_work_mem to reflect the 1GB limitation with VACUUM

From: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
To: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
Cc: Martín Marqués <martin(dot)marques(at)gmail(dot)com>, pgsql-docs(at)lists(dot)postgresql(dot)org
Subject: Re: Update maintenance_work_mem/autovacuum_work_mem to reflect the 1GB limitation with VACUUM
Date: 2021-06-02 09:16:08
Message-ID: CAD21AoAv5gdFEggmHj-GeSVvkZkhv1fvLf3xe8aPUS7y8tOTNg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs pgsql-hackers

On Wed, May 5, 2021 at 7:03 PM Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> wrote:
>
> On Mon, 2021-05-03 at 13:48 -0300, Martín Marqués 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,

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

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Peter Eisentraut 2021-06-02 15:00:54 Re: Note that ALTER TABLE cannot alter generated stored columns
Previous Message Greg Sabino Mullane 2021-06-01 19:25:18 Re: Update maintenance_work_mem/autovacuum_work_mem to reflect the 1GB limitation with VACUUM

Browse pgsql-hackers by date

  From Date Subject
Next Message houzj.fnst@fujitsu.com 2021-06-02 09:33:26 RE: Parallel INSERT SELECT take 2
Previous Message tanghy.fnst@fujitsu.com 2021-06-02 09:07:08 RE: [BUG]Update Toast data failure in logical replication