Re: pg_receivexlog --create-slot-if-not-exists

From: Andres Freund <andres(at)anarazel(dot)de>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Stephen Frost <sfrost(at)snowman(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_receivexlog --create-slot-if-not-exists
Date: 2015-06-19 15:21:46
Message-ID: 20150619152146.GI29350@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2015-06-19 11:19:23 -0400, Magnus Hagander wrote:
> On Fri, Jun 19, 2015 at 11:17 AM, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
>
> > * Andres Freund (andres(at)anarazel(dot)de) wrote:
> > > To make slot usage in pg_receivexlog easier, should we add
> > > --create-slot-if-not-exists? That'd mean you could run the same command
> > > the first and later invocation.
> >
> > Yes, please.
>
> +1.

Arguably we could do that for 9.5 - the whole slot stuff for receivexlog
is new, and this is just adjusting the API slightly. I won't fight much
for that opinion though.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2015-06-19 15:33:39 Re: checkpointer continuous flushing
Previous Message Cédric Villemain 2015-06-19 15:21:25 Re: pg_receivexlog --create-slot-if-not-exists