Re: [HACKERS] Function to control physical replication slot - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: [HACKERS] Function to control physical replication slot
Date
Msg-id 975f082d-7d0d-de3b-90c8-5adf394f7906@2ndquadrant.com
Whole thread Raw
In response to [HACKERS] Function to control physical replication slot  (Magnus Hagander <magnus@hagander.net>)
Responses Re: [HACKERS] Function to control physical replication slot  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
On 4/11/17 05:15, Magnus Hagander wrote:
> Is there a particular reason we don't have a function to *set* the
> restart_lsn of a replication slot, other than to drop it and recreate it?

I suppose there could be lots of problems if the LSN you specify isn't
valid.  And it might be hard to determine whether a given LSN is valid.

If this could be made to work, this would actually offer an interesting
option for dumping and restoring subscriptions.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: [HACKERS] pg_statistic_ext.staenabled might not be the best column name
Next
From: Andres Freund
Date:
Subject: Re: [HACKERS] snapbuild woes