Re: [COMMITTERS] pgsql: Allow time delayed standbys and recovery

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Thom Brown <thom(at)linux(dot)com>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, Simon Riggs <simon(dot)riggs(at)enterprisedb(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: [COMMITTERS] pgsql: Allow time delayed standbys and recovery
Date: 2022-04-08 13:36:27
Message-ID: CA+TgmobvQ2mHsz47Z_jBoRONOx8yutXbJOsA-MuXLUp_UjhLag@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On Wed, Apr 6, 2022 at 8:15 AM Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Tue, Apr 5, 2022 at 8:43 PM Thom Brown <thom(at)linux(dot)com> wrote:
> > I share your discomfort with the wording. How about:
> >
> > WAL records must be kept on standby until they are ready to be applied.
> > Therefore, longer delays will result in a greater accumulation of WAL files,
> > increasing disk space requirements for the standby's <filename>pg_wal</>
> > directory.
>
> Looks awesome.

Here that is in patch form. I feel that the feature freeze should not
preclude committing this documentation improvement, but if someone
feels otherwise, then I will leave this until the tree reopens.

--
Robert Haas
EDB: http://www.enterprisedb.com

Attachment Content-Type Size
v1-0001-docs-Note-the-recovery_min_apply_delay-bloats-pg_.patch application/octet-stream 1.4 KB

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Magnus Hagander 2022-04-08 13:45:18 Re: [COMMITTERS] pgsql: Allow time delayed standbys and recovery
Previous Message Peter Eisentraut 2022-04-08 13:16:50 pgsql: psql: Fix translation marking

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2022-04-08 13:39:18 Re: Add parameter jit_warn_above_fraction
Previous Message Greg Stark 2022-04-08 13:33:14 Re: Support for grabbing multiple consecutive values with nextval()