Re: [HACKERS] pg_stop_backup(wait_for_archive := true) on standbyserver - Mailing list pgsql-hackers

From David Steele
Subject Re: [HACKERS] pg_stop_backup(wait_for_archive := true) on standbyserver
Date
Msg-id e5ab7783-89a4-45d9-ffd5-9e9117573c1d@pgmasters.net
Whole thread Raw
In response to Re: [HACKERS] pg_stop_backup(wait_for_archive := true) on standbyserver  (David Steele <david@pgmasters.net>)
List 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@pgmasters.net



pgsql-hackers by date:

Previous
From: Gilles Darold
Date:
Subject: Re: [HACKERS] Issue with circular references in VIEW
Next
From: Robert Haas
Date:
Subject: Re: [HACKERS] Mishandling of WCO constraints in direct foreign table modification