Re: [COMMITTERS] pgsql: Allow time delayed standbys and recovery
Magnus Hagander <magnus@hagander.net>
From: Magnus Hagander <magnus@hagander.net>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Thom Brown <thom@linux.com>, Simon Riggs <simon.riggs@enterprisedb.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2022-04-08T13:45:18Z
Lists: 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) -- Magnus Hagander Me: https://www.hagander.net/ <http://www.hagander.net/> Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>
Commits
-
docs: Note the recovery_min_apply_delay bloats pg_wal.
- ad385a494f6a 15.0 landed
-
Allow time delayed standbys and recovery
- 36da3cfb457b 9.4.0 cited