From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_receivexlog and replication slots |
Date: | 2014-07-11 09:23:59 |
Message-ID: | 20140711092359.GB25051@awork2.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2014-07-11 11:18:58 +0200, Magnus Hagander wrote:
> On Fri, Jul 11, 2014 at 11:14 AM, Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
> > On 2014-07-11 11:08:48 +0200, Magnus Hagander wrote:
> >> Is there a particular reason why pg_receivexlog only supports using
> >> manually created slots but pg_recvlogical supports creating and
> >> dropping them? Wouldn't it be good for consistency there?
> >
> > I've added it to recvlogical because logical decoding isn't usable
> > without slots. I'm not sure what you'd want to create/drop a slot from
> > receivexlog for, but I'm not adverse to adding the capability.
>
> I was mostly thinking for consistency, really. Using slots with
> pg_receivexlog makes quite a bit of sense, even though it's useful
> without it. But having the ability to create and drop (with compatible
> commandline arguments of course) them directly when you set it up
> would certainly be more convenient.
Ok. Do you plan to take care of it? If, I'd be fine with backpatching
it. I'm not likely to get to it right now :(
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Christoph Berg | 2014-07-11 09:39:23 | Re: Securing "make check" (CVE-2014-0067) |
Previous Message | Tomas Vondra | 2014-07-11 09:23:21 | Re: tweaking NTUP_PER_BUCKET |