Re: Function to control physical replication slot

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Function to control physical replication slot
Date: 2017-04-13 00:15:52
Message-ID: 975f082d-7d0d-de3b-90c8-5adf394f7906@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2017-04-13 00:29:59 Re: snapbuild woes
Previous Message Tomas Vondra 2017-04-12 23:37:17 Re: pg_statistic_ext.staenabled might not be the best column name