Re: A failure in prepared_xacts test
Richard Guo <guofenglinux@gmail.com>
From: Richard Guo <guofenglinux@gmail.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2024-04-29T09:11:19Z
Lists: pgsql-hackers
On Mon, Apr 29, 2024 at 2:58 PM Michael Paquier <michael@paquier.xyz> wrote: > On Mon, Apr 29, 2024 at 01:32:40AM -0400, Tom Lane wrote: > > (BTW, on the same logic, should ecpg's twophase.pgc be using a > > prepared-transaction name that's less generic than "gxid"?) > > I've hesitated a few seconds about that before sending my patch, but > refrained because this stuff does not care about the contents of > pg_prepared_xacts. I'd be OK to use something like an "ecpg_regress" > or something similar there. I noticed that some TAP tests from recovery and subscription would select the count from pg_prepared_xacts. I wonder if these tests would be affected if there are any prepared transactions on the backend. Thanks Richard
Commits
-
Remove auth-options support from initdb
- 83ae824c87a5 17.0 landed
-
Make two-phase tests of ECPG and main suite more concurrent-proof
- 7e61e4cc7cfc 17.0 landed
-
initdb: Add options --auth-local and --auth-host
- 8a02339e9ba3 9.2.0 cited