pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: hubert depesz lubaczewski <depesz@depesz.com>
To: Laurenz Albe <laurenz.albe@cybertec.at>
Cc: pgsql-general <pgsql-general@lists.postgresql.org>
Subject: Re: How can I change replication slot's restart_lsn from SQL?
Date: Wed, 17 May 2023 08:21:17 +0200
Message-ID: <ZGRyXYfkj0G6xdon@depesz.com> (raw)
In-Reply-To: <fec2f1b6fd59ead3bb495be039b2785cc4c11810.camel@cybertec.at>
References: <ZGORxidIQbYlZObB@depesz.com>
	<ZGO+2JzKJ4xRqxJK@depesz.com>
	<fec2f1b6fd59ead3bb495be039b2785cc4c11810.camel@cybertec.at>

On Wed, May 17, 2023 at 08:16:41AM +0200, Laurenz Albe wrote:
> On Tue, 2023-05-16 at 19:35 +0200, hubert depesz lubaczewski wrote:
> > > I'm working on a workaround for a bug in Pg
> > > (https://www.postgresql.org/message-id/flat/Yz2hivgyjS1RfMKs%40depesz.com)
> > > I want to create replication slot, and advance is manually, keeping it
> > > always a bit lagging behind real replication slot.
> > > 
> > > I can create slot, no problem:
> > > select pg_create_logical_replication_slot('depesz', 'test_decoding');
> > > and then I can, theoretically, advance it to whatever position with
> > > select * from pg_replication_slot_advance('depesz', '...');
> > > 
> > > *BUT* - it changes only confirmed_flush_lsn, leaving restart_lsn as it
> > > was.
> > > 
> > > How can I advance restart_lsn of a slot?
> > > 
> > > Generally my idea is to get lsn from real replication slot, subtract,
> > > let's say 1GB from it, and advance my "fake slot" to this value, this
> > > keeping always buffer of 1GB in case the bug with removed wal happened
> > > again.
> > > 
> > > I will be doing this on Pg12, which can limit my options, but perhaps
> > > there is some way to do it via plain(ish) SQL ?
> > 
> > if doing it via SQL is not an option, is there any way to have
> > replication slot and modify it's restart_lsn, regardless of whether it
> > will b e physical, or logical, and what tool shoudl I use.
> > 
> > I tried with pg_recvlogical, and read
> > https://www.postgresql.org/docs/current/protocol-replication.html but
> > I don't see how I can make restart_lsn advance to anything.
> 
> You could shutdown the server and edit the file in "pg_replslot" with
> a hex editor.  Not very convenient, and you'd have to study the source
> to understand the format of the file.

OK. Shutting down production server every 5 minutes to advance the slot
isn't really an option.

How do "normal" wal consumers update restart_lsn? Is there a reason why
it can't be done using pg_rec(eive|v)* ?

Best regards,

depesz






view thread (5+ messages)  latest in thread

Message-ID: <ZGRyXYfkj0G6xdon@depesz.com>
Permalink:  ../ZGRyXYfkj0G6xdon@depesz.com/
Also on:    postgresql.org/message-id/ZGRyXYfkj0G6xdon@depesz.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-general@postgresql.org
  Cc: depesz@depesz.com, laurenz.albe@cybertec.at
  Subject: Re: How can I change replication slot's restart_lsn from SQL?
  In-Reply-To: <ZGRyXYfkj0G6xdon@depesz.com>
  References: <ZGORxidIQbYlZObB@depesz.com> <ZGO+2JzKJ4xRqxJK@depesz.com> <fec2f1b6fd59ead3bb495be039b2785cc4c11810.camel@cybertec.at> <ZGRyXYfkj0G6xdon@depesz.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox