Re: pg_receivexlog and replication slots - Mailing list pgsql-hackers

From Andres Freund
Subject Re: pg_receivexlog and replication slots
Date
Msg-id 20140711091422.GA25051@awork2.anarazel.de
Whole thread Raw
In response to pg_receivexlog and replication slots  (Magnus Hagander <magnus@hagander.net>)
Responses Re: pg_receivexlog and replication slots
List pgsql-hackers
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'm guessing it's related to not being exposed over the replication
> protocol?

It's exposed:
create_replication_slot:        /* CREATE_REPLICATION_SLOT slot PHYSICAL */        K_CREATE_REPLICATION_SLOT IDENT
K_PHYSICAL

Greetings,

Andres Freund

-- Andres Freund                       http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training &
Services



pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: pg_receivexlog and replication slots
Next
From: Magnus Hagander
Date:
Subject: Re: pg_receivexlog and replication slots