On Sun, 15 Dec 2024 at 10:00, Alexander Lakhin <exclus...@gmail.com> wrote: > shows that the subscription and publication tests are not concurrent-safe, > because modifying the same pg_database entry might fail with the "tuple > concurrently updated" error.
This seems related to this thread about concurrency issues in ALTER/DROP SUBSCRIPTION[1], except that this is for GRANT/REVOKE it seems. The easiest way to address the flakiness of this test though is probably to just don't run these tests in in parallel. See attached. [1]: https://www.postgresql.org/message-id/flat/HE1PR8303MB0075BF78AF1BE904050DA16BF7729%40HE1PR8303MB0075.EURPRD83.prod.outlook.com
v1-0001-Don-t-run-flaky-tests-in-parallel-with-eachother.patch
Description: Binary data
