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 1nIHHh-00049g-9P for pgsql-hackers@arkaria.postgresql.org; Thu, 10 Feb 2022 21:47:25 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nIHHf-0002Y9-4u for pgsql-hackers@arkaria.postgresql.org; Thu, 10 Feb 2022 21:47:23 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nIHHe-0002Y0-SC for pgsql-hackers@lists.postgresql.org; Thu, 10 Feb 2022 21:47:22 +0000 Received: from momjian.us ([72.94.173.45]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nIHHc-0006eB-5A for pgsql-hackers@postgresql.org; Thu, 10 Feb 2022 21:47:21 +0000 Received: from bruce by momjian.us with local (Exim 4.94.2) (envelope-from ) id 1nIHHX-008VCB-G1; Thu, 10 Feb 2022 16:47:15 -0500 Date: Thu, 10 Feb 2022 16:47:15 -0500 From: Bruce Momjian To: Ashutosh Sharma Cc: Andres Freund , Peter Eisentraut , pgsql-hackers Subject: Re: Synchronizing slots from primary to standby Message-ID: References: <514f6f2f-6833-4539-39f1-96cd1e011f23@enterprisedb.com> <18dbc929-a281-8552-4f1d-7e4d0e4eedba@enterprisedb.com> <646acd8d-9896-ed8d-2ab4-0bf11b3285d4@enterprisedb.com> <20220205195944.drwc3psrb5udt2cw@alap3.anarazel.de> <20220207203222.22aktwxrt3fcllru@alap3.anarazel.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Tue, Feb 8, 2022 at 08:27:32PM +0530, Ashutosh Sharma wrote: > > Which means that if e.g. the standby_slot_names GUC differs from > > synchronize_slot_names on the physical replica, the slots synchronized on the > > physical replica are not going to be valid. Or if the primary drops its > > logical slots. > > > > > > > Should the redo function for the drop replication slot have the capability > > > to drop it on standby and its subscribers (if any) as well? > > > > Slots are not WAL logged (and shouldn't be). > > > > I think you pretty much need the recovery conflict handling infrastructure I > > referenced upthread, which recognized during replay if a record has a conflict > > with a slot on a standby. And then ontop of that you can build something like > > this patch. > > > > OK. Understood, thanks Andres. I would love to see this feature in PG 15. Can someone explain its current status? Thanks. -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com If only the physical world exists, free will is an illusion.