Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pzAXL-0007Yl-SF for pgsql-general@arkaria.postgresql.org; Wed, 17 May 2023 06:21:24 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pzAXK-0007s8-P9 for pgsql-general@arkaria.postgresql.org; Wed, 17 May 2023 06:21:22 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pzAXK-0007ry-DI for pgsql-general@lists.postgresql.org; Wed, 17 May 2023 06:21:22 +0000 Received: from lana.depesz.com ([88.198.49.178] helo=depesz.com) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1pzAXG-000I6Y-KQ for pgsql-general@lists.postgresql.org; Wed, 17 May 2023 06:21:21 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=depesz.com; s=20170201; h=In-Reply-To:Content-Transfer-Encoding:Content-Type:MIME-Version :References:Reply-To:Message-ID:Subject:Cc:To:Sender:From:Date:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=R0kxXx2E3vdKFoqBgrjcsLlVetNVhaz0Fw4+nhxBvSY=; b=qY3UtDJj7iVD9kbrRrQL+KQ6A5 TuhFMy1K3WzG01hU0Vb3iOyT8ihICgDXKcAs3hwgsD6p3UBuvS9nfJEBHf6ECpO08kLalnbfheqwv VUdkLd/JKWTB0vTmgOSFIRZnUjgrTk9VS2+RzZAygPkDeMECVze+eZhW+xqEKjXBO8Go=; Received: from depesz by depesz.com with local (Exim 4.94.2) (envelope-from ) id 1pzAXF-00Fntk-Oz; Wed, 17 May 2023 08:21:17 +0200 Date: Wed, 17 May 2023 08:21:17 +0200 From: hubert depesz lubaczewski Sender: depesz@depesz.com To: Laurenz Albe Cc: pgsql-general Subject: Re: How can I change replication slot's restart_lsn from SQL? Message-ID: Reply-To: depesz@depesz.com References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk 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