Re: pgsql: Introduce replication slots. - Mailing list pgsql-committers

From Thom Brown
Subject Re: pgsql: Introduce replication slots.
Date
Msg-id CAA-aLv79Do9KjUMqT-W1cffirLn0MJpNQQThc2+aTXUKbqz1Rw@mail.gmail.com
Whole thread Raw
In response to Re: pgsql: Introduce replication slots.  (Andres Freund <andres@2ndquadrant.com>)
List pgsql-committers
On 28 February 2014 19:22, Andres Freund <andres@2ndquadrant.com> wrote:
On 2014-02-28 19:05:40 +0000, Thom Brown wrote:
> On 1 February 2014 03:50, Robert Haas <rhaas@postgresql.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. 

Yes, that fixes the problem.  Thanks.  I can stop quadruple-checking my config now. :)

--
Thom

pgsql-committers by date:

Previous
From: Andres Freund
Date:
Subject: Re: pgsql: Introduce replication slots.
Next
From: Tom Lane
Date:
Subject: pgsql: Allow regex operations to be terminated early by query cancel re