Re: [HACKERS] Function to control physical replication slot

2017-04-13 Thread Magnus Hagander
On Thu, Apr 13, 2017 at 2:40 AM, Andres Freund wrote: > On 2017-04-12 20:15:52 -0400, Peter Eisentraut wrote: > > 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 re

Re: [HACKERS] Function to control physical replication slot

2017-04-12 Thread Andres Freund
On 2017-04-12 20:15:52 -0400, Peter Eisentraut wrote: > 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

Re: [HACKERS] Function to control physical replication slot

2017-04-12 Thread Peter Eisentraut
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

[HACKERS] Function to control physical replication slot

2017-04-11 Thread Magnus Hagander
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? Similarly, to create one with a fixed value for restart_lsn and not necessarily the one the machine is at right now? Basically I'm doing a small script that