On 16.06.21 07:22, shinya11.k...@nttdata.com wrote:
As shown below, the argument types of autovacuum_vacuum_insert_scale_factor and
toast.autovacuum_vacuum_insert_scale_factor are different from the others.
---
autovacuum_vacuum_scale_factor, toast.autovacuum_vacuum_scale_factor (floating
point
On 2021-Jun-24, Bruce Momjian wrote:
> + As a safety device, an aggressive vacuum scan will
> + occur for any table whose multixact-age (see + linkend="vacuum-for-multixact-wraparound"/>) is greater than + linkend="guc-autovacuum-multixact-freeze-max-age"/>. Also, if the
> +
On Tue, Jun 22, 2021 at 08:32:18AM +0200, Laurenz Albe wrote:
> > What does "the amount of used member storage space exceeds 50% of the
> > addressable storage space" mean?
>
> You are right. See MultiXactMemberFreezeThreshold for the whole story.
>
> What about:
>
> As a safety device, an ag
On Thu, Jun 24, 2021 at 4:20 AM Peter Eisentraut <
peter.eisentr...@enterprisedb.com> wrote:
> On 04.06.21 02:08, David G. Johnston wrote:
> > The example in the update documentation that does an upsert using a
> > savepoint seems like it should just go away now that we have insert...on
> > confli
On 14.06.21 18:29, Bruce Momjian wrote:
On Sat, Jun 12, 2021 at 12:48:25PM -0700, David G. Johnston wrote:
On Sat, Jun 12, 2021, 12:28 PG Doc comments form
wrote:
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/13/tutorial-f
On 04.06.21 02:08, David G. Johnston wrote:
The example in the update documentation that does an upsert using a
savepoint seems like it should just go away now that we have insert...on
conflict. Making an explicit reference (and link) to that feature in
the Update documentation should be added
