Re: [HACKERS] Function to move the position of a replication slot - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: [HACKERS] Function to move the position of a replication slot
Date
Msg-id CABUevEz8kg=8e1nqAhQCrdFvhYfCe914gvLgQ82vV9WBc=FtkQ@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Function to move the position of a replication slot  (Craig Ringer <craig@2ndquadrant.com>)
Responses Re: [HACKERS] Function to move the position of a replication slot  (Craig Ringer <craig@2ndquadrant.com>)
List pgsql-hackers
On Thu, May 4, 2017 at 2:42 PM, Craig Ringer <craig@2ndquadrant.com> wrote:
On 4 May 2017 at 20:05, Magnus Hagander <magnus@hagander.net> wrote:
> PFA a patch that adds a new function, pg_move_replication_slot, that makes
> it possible to move the location of a replication slot without actually
> consuming all the WAL on it.

> This can be useful for example to keep replication slots in sync between
> different servers in a replication cluster.

It needs a test to ensure it only operates on physical slots. It
should ERROR on a logical slot, since it has no way of correctly
advancing the catalog_xmin or finding a reasonable restart_lsn  for
logical decoding.

I guess that makes sense, yeah. I didn't try it with that :)

 
I'm still fine with the name, since I plan to add that capability in
pg11 by running through logical decoding and ReorderBufferSkip()ing
each xact until we reach the target lsn.

Cool.
 
--

pgsql-hackers by date:

Previous
From: Craig Ringer
Date:
Subject: Re: [HACKERS] Function to move the position of a replication slot
Next
From: Craig Ringer
Date:
Subject: Re: [HACKERS] Function to move the position of a replication slot