On Tue, Sep 12, 2017 at 7:35 PM, Jeff Janes wrote:
> On Wed, Sep 6, 2017 at 2:50 AM, Alvaro Herrera
> wrote:
>
>> Magnus Hagander wrote:
>> > On Mon, Sep 4, 2017 at 3:21 PM, Jeff Janes
>> wrote:
>>
>> > > Should the parent
On Wed, Sep 6, 2017 at 2:50 AM, Alvaro Herrera
wrote:
> Magnus Hagander wrote:
> > On Mon, Sep 4, 2017 at 3:21 PM, Jeff Janes wrote:
>
> > > Should the parent process of pg_basebackup be made to respond to
> SIGCHLD?
> > > Or call waitpid(bgchild,
On Wed, Sep 6, 2017 at 11:50 AM, Alvaro Herrera
wrote:
> Magnus Hagander wrote:
> > On Mon, Sep 4, 2017 at 3:21 PM, Jeff Janes wrote:
>
> > > Should the parent process of pg_basebackup be made to respond to
> SIGCHLD?
> > > Or call waitpid(bgchild,
Magnus Hagander wrote:
> On Mon, Sep 4, 2017 at 3:21 PM, Jeff Janes wrote:
> > Should the parent process of pg_basebackup be made to respond to SIGCHLD?
> > Or call waitpid(bgchild, , WNOHANG) in some strategic loop?
>
> I think it's ok to just call waitpid() -- we don't
On Mon, Sep 4, 2017 at 3:21 PM, Jeff Janes wrote:
>
> If I tell pg_basebackup to use a non-existent slot, it immediately reports
> an error. And then it exits with an error, but only after streaming the
> entire database contents.
>
> If you are doing this interactively
If I tell pg_basebackup to use a non-existent slot, it immediately reports
an error. And then it exits with an error, but only after streaming the
entire database contents.
If you are doing this interactively and are on the ball, of course, you can
hit ctrl-C when you see the error message.
I