Re: [COMMITTERS] pgsql: Allow time delayed standbys and recovery - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: [COMMITTERS] pgsql: Allow time delayed standbys and recovery
Date
Msg-id CABUevEy5DZA77yc2cWfSsOg1UsaEy7=ZU1Kd4NdkX=zvwy3yig@mail.gmail.com
Whole thread Raw
In response to Re: [COMMITTERS] pgsql: Allow time delayed standbys and recovery  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers


On Fri, Apr 8, 2022 at 3:36 PM Robert Haas <robertmhaas@gmail.com> wrote:
On Wed, Apr 6, 2022 at 8:15 AM Robert Haas <robertmhaas@gmail.com> wrote:
> On Tue, Apr 5, 2022 at 8:43 PM Thom Brown <thom@linux.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.

We normally allow documentation and bug fixes after the feature freeze. (It's only in the "we're about to wrap the release right now"-freeze that we have to avoid those)
 
--

pgsql-hackers by date:

Previous
From: Bharath Rupireddy
Date:
Subject: Re: How to simulate sync/async standbys being closer/farther (network distance) to primary in core postgres?
Next
From: Dave Cramer
Date:
Subject: Re: GSoC: New and improved website for pgjdbc (JDBC)