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

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: Martín Marqués <martin(dot)marques(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Update maintenance_work_mem/autovacuum_work_mem to reflect the 1GB limitation with VACUUM
Date: 2021-05-20 15:52:38
Message-ID: f311f6eda1bd8a6c319a969881b0c15e6fbbfaa8.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs pgsql-hackers

On Wed, 2021-05-05 at 12:03 +0200, Laurenz Albe 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

Just sending a reply to -hackers so I can add it to the commitfest.

Yours,
Laurenz Albe

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Laurenz Albe 2021-05-20 15:53:40 Re: Clarify how triggers relate to transactions
Previous Message Pavel Luzanov 2021-05-20 12:44:52 Re: pg_monitor role description

Browse pgsql-hackers by date

  From Date Subject
Next Message Laurenz Albe 2021-05-20 15:53:40 Re: Clarify how triggers relate to transactions
Previous Message Bharath Rupireddy 2021-05-20 15:44:45 Re: Alias collision in `refresh materialized view concurrently`