Re: gitlab post-mortem: pg_basebackup waiting for checkpoint
Robert Haas <robertmhaas@gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Magnus Hagander <magnus@hagander.net>,
Michael Banck <michael.banck@credativ.de>, Jim Nasby <Jim.Nasby@bluetreble.com>,
Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2017-02-14T23:18:24Z
Lists: pgsql-hackers
On Tue, Feb 14, 2017 at 4:06 PM, Alvaro Herrera <alvherre@2ndquadrant.com> wrote: > I'd rather have a --quiet mode instead. If you're running it by hand, > you're likely to omit the switch, whereas when writing the cron job > you're going to notice lack of switch even before you let the job run > once. Well, that might've been a better way to design it, but changing it now would break backward compatibility and I'm not really sure that's a good idea. Even if it is, it's a separate concern from whether or not in the less-quiet mode we should point out that we're waiting for a checkpoint on the server side. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
Commits
-
Back-patch checkpoint clarification docs and pg_basebackup updates
- bd34e7f19b40 9.4.12 landed
- 2843d5d657be 9.5.7 landed
- b88b929a7071 9.6.3 landed