Re: PATCH: Make pg_stop_backup() archive wait optional

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: David Steele <david(at)pgmasters(dot)net>
Cc: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PATCH: Make pg_stop_backup() archive wait optional
Date: 2017-03-22 15:37:03
Message-ID: 20170322153703.GK9812@tamriel.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

David, all,

* David Steele (david(at)pgmasters(dot)net) wrote:
> On 3/21/17 2:34 PM, Fujii Masao wrote:
> >The patch basically looks good to me, but one comment is;
> >backup.sgml (at least the description for "Making a non-exclusive
> >low level backup) seems to need to be updated.
>
> Agreed. Added in the attached patch and rebased on 8027556.

I've started looking at this. Seems pretty straight-forward and will
try to get it committed later today.

Thanks!

Stephen

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2017-03-22 15:39:20 Re: [COMMITTERS] pgsql: Sync pg_dump and pg_dumpall output
Previous Message Peter Eisentraut 2017-03-22 15:29:06 Re: logical replication access control patches