Re: A failure in prepared_xacts test
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Richard Guo <guofenglinux@gmail.com>
Cc: Michael Paquier <michael@paquier.xyz>,
PostgreSQL-development <pgsql-hackers@postgresql.org>,
Alexander Lakhin <exclusion@gmail.com>
Date: 2024-04-30T01:48:13Z
Lists: pgsql-hackers
Richard Guo <guofenglinux@gmail.com> writes: > +1. I'm kind of worried that the expansion of parallelization could > lead to more instances of instability. Alexander mentioned one such > case at [1]. I haven't looked into it though. > [1] https://www.postgresql.org/message-id/cbf0156f-5aa1-91db-5802-82435dda03e6%40gmail.com The mechanism there is pretty obvious: a plancache flush happened at just the wrong (right?) time and caused the output to change, as indeed the comment acknowledges: -- currently, this fails due to cached plan for "r.f1 + 1" expression -- (but if debug_discard_caches is on, it will succeed) I wonder if we shouldn't just remove that test case as being too unstable -- especially since it's not proving much anyway. regards, tom lane
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