From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
---|---|
To: | Thom Brown <thom(at)linux(dot)com> |
Cc: | Robert Haas <rhaas(at)postgresql(dot)org>, pgsql-committers <pgsql-committers(at)postgresql(dot)org> |
Subject: | Re: pgsql: Introduce replication slots. |
Date: | 2014-02-28 19:22:38 |
Message-ID: | 20140228192238.GK15628@awork2.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
On 2014-02-28 19:05:40 +0000, Thom Brown wrote:
> On 1 February 2014 03:50, Robert Haas <rhaas(at)postgresql(dot)org> wrote:
>
> > Introduce replication slots.
> >
> > Replication slots are a crash-safe data structure which can be created
> > on either a master or a standby to prevent premature removal of
> > write-ahead log segments needed by a standby, as well as (with
> > hot_standby_feedback=on) pruning of tuples whose removal would cause
> > replication conflicts. Slots have some advantages over existing
> > techniques, as explained in the documentation.
> >
> > In a few places, we refer to the type of replication slots introduced
> > by this patch as "physical" slots, because forthcoming patches for
> > logical decoding will also have slots, but with somewhat different
> > properties.
> >
>
> So now that I've actually gone to use physical replication slots, I can't
> get them working.
Aw yuck. Try a shorter name. libpqrcv_startstreaming is truncating the
identifier if it's too long...
Patch fixing that attached.
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
Attachment | Content-Type | Size |
---|---|---|
use-sufficiently-large-buf.patch | text/x-patch | 587 bytes |
From | Date | Subject | |
---|---|---|---|
Next Message | Thom Brown | 2014-02-28 19:33:51 | Re: pgsql: Introduce replication slots. |
Previous Message | Thom Brown | 2014-02-28 19:05:40 | Re: pgsql: Introduce replication slots. |