Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rPEHP-00A8az-6V for pgsql-hackers@arkaria.postgresql.org; Mon, 15 Jan 2024 04:08:55 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1rPEHN-00DLSs-3t for pgsql-hackers@arkaria.postgresql.org; Mon, 15 Jan 2024 04:08:53 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rPEHM-00DLSi-QX for pgsql-hackers@lists.postgresql.org; Mon, 15 Jan 2024 04:08:52 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rPEHG-001rKZ-12 for pgsql-hackers@lists.postgresql.org; Mon, 15 Jan 2024 04:08:52 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 40F48dx81375924; Sun, 14 Jan 2024 23:08:39 -0500 From: Tom Lane To: Michael Paquier cc: Bertrand Drouvot , Alexander Lakhin , "Yu Shi (Fujitsu)" , Robert Haas , Andres Freund , Thomas Munro , PostgreSQL Hackers Subject: Re: Test slots invalidations in 035_standby_logical_decoding.pl only if dead rows are removed In-reply-to: References: <7c025095-5763-17a6-8c80-899b35bd0459@gmail.com> <5d0e5bec-67f9-9164-36cb-c4ff5f95d1ed@gmail.com> <6f85667e-5754-5d35-dbf1-c83fe08c1e48@gmail.com> Comments: In-reply-to Michael Paquier message dated "Mon, 15 Jan 2024 12:59:01 +0900" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1375922.1705291719.1@sss.pgh.pa.us> Date: Sun, 14 Jan 2024 23:08:39 -0500 Message-ID: <1375923.1705291719@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Michael Paquier writes: > While thinking about that, a second idea came into my mind: a > superuser-settable developer GUC to disable such WAL records to be > generated within certain areas of the test. This requires a small > implementation, but nothing really huge, while being portable > everywhere. And it is not the first time I've been annoyed with these > records when wanting a predictible set of WAL records for some test > case. Hmm ... I see what you are after, but to what extent would this mean that what we are testing is not our real-world behavior? regards, tom lane