| From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Function to move the position of a replication slot |
| Date: | 2017-05-04 12:42:26 |
| Message-ID: | CAMsr+YFYdqpK+m_zXCL4ig5rJE_oTNGsyKMi-so6=a2arpAjkw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 4 May 2017 at 20:05, Magnus Hagander <magnus(at)hagander(dot)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'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.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2017-05-04 12:45:49 | Re: Function to move the position of a replication slot |
| Previous Message | Neha Sharma | 2017-05-04 12:39:54 | Re: delta relations in AFTER triggers |