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 1v6CDI-000nZp-Lu for pgsql-hackers@arkaria.postgresql.org; Tue, 07 Oct 2025 18:15:04 +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 1v6CDG-0028gC-HJ for pgsql-hackers@arkaria.postgresql.org; Tue, 07 Oct 2025 18:15:03 +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 1v6CDG-0028fo-7X for pgsql-hackers@lists.postgresql.org; Tue, 07 Oct 2025 18:15:03 +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.96) (envelope-from ) id 1v6CDE-000twb-2Y for pgsql-hackers@postgresql.org; Tue, 07 Oct 2025 18:15:02 +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 597IEopa2495354; Tue, 7 Oct 2025 14:14:50 -0400 From: Tom Lane To: "Joel Jacobson" cc: "Matheus Alcantara" , pgsql-hackers Subject: Re: Optimize LISTEN/NOTIFY In-reply-to: <85828f29-e72e-4400-94f3-9a69bc8dc239@app.fastmail.com> References: <6899c044-4a82-49be-8117-e6f669765f7e@app.fastmail.com> <165530.1752362320@sss.pgh.pa.us> <02a7cd37-e2fc-4212-8b19-f8c239c95fb8@app.fastmail.com> <96f00bf1-cc9d-4520-9d02-9e14e7767c88@app.fastmail.com> <30c2aa7d-dd6c-4b68-a2e4-f217a1a34acf@app.fastmail.com> <0b4d402a-9ac2-4aa8-acf8-8231dbe579ea@app.fastmail.com> <3095599.1758644879@sss.pgh.pa.us> <0dc6a2cc-5216-4dc1-9dd2-430cafc6095b@app.fastmail.com> <52CC167F-763B-4ECA-B0B4-DAB381816828@gmail.com> <9186C6D0-F7A9-482A-9183-89E530B57E36@gmail.com> <1073593.1759423179@sss.pgh.pa.us> <4bd5e6c4-6fa7-44bb-869d-59a32a331fa8@app.fastmail.com> <85828f29-e72e-4400-94f3-9a69bc8dc239@app.fastmail.com> Comments: In-reply-to "Joel Jacobson" message dated "Tue, 07 Oct 2025 19:28:22 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2495352.1759860890.1@sss.pgh.pa.us> Date: Tue, 07 Oct 2025 14:14:50 -0400 Message-ID: <2495353.1759860890@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk "Joel Jacobson" writes: >> 7. I'm wondering if we could add some TAP tests for this? I think that >> adding a case to ensure that we can grown the dshash correctly and also >> we manage multiple backends to the same channel properly. This CF [1] >> has some examples of how TAP tests can be created to test LISTEN/NOTIFY > I will look over the tests. Maybe we should add some elog DEBUG at the > new code paths, and ensure the tests at least cover all of them? I went to do a coverage test on v10, and found that it does not get through the existing async-notify isolation test: it panics with "cannot abort transaction %u, it was already committed". It's a bit premature to worry about adding new tests if you're not passing the ones that are there. regards, tom lane