Re: pg_stop_backup(wait_for_archive := true) on standby server

From: David Steele <david(at)pgmasters(dot)net>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: pg_stop_backup(wait_for_archive := true) on standby server
Date: 2017-07-24 19:59:32
Message-ID: e5ab7783-89a4-45d9-ffd5-9e9117573c1d@pgmasters.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 7/24/17 3:28 PM, David Steele wrote:
>
> Yes, and this is another behavioral change to consider -- one that is
> more likely to impact users than the change to pg_stop_backup(). If
> pg_basebackup is not currently waiting for WAL on a standby (but does on
> a primary) then that's pretty serious.

My bad, before PG10 pg_basebackup did not check that WAL was archived on
a primary *or* a standby unless the -x option was specified, as documented.

--
-David
david(at)pgmasters(dot)net

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2017-07-24 20:35:30 Re: Mishandling of WCO constraints in direct foreign table modification
Previous Message Gilles Darold 2017-07-24 19:43:33 Re: Issue with circular references in VIEW