| From: | Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> |
|---|---|
| To: | Alexander Lakhin <exclusion(at)gmail(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Parallel tests publication and subscription might fail due to concurrent tuple update |
| Date: | 2024-12-15 11:01:07 |
| Message-ID: | CAGECzQTTfKH0yRqv_2kpkLzBwhSk-2=d8+8XkeVDoFFDqRve-Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, 15 Dec 2024 at 10:00, Alexander Lakhin <exclusion(at)gmail(dot)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.
| Attachment | Content-Type | Size |
|---|---|---|
| v1-0001-Don-t-run-flaky-tests-in-parallel-with-eachother.patch | application/octet-stream | 1022 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vladimír Houba jr. | 2024-12-15 11:04:14 | transaction priority feature request |
| Previous Message | Alexander Lakhin | 2024-12-15 09:00:00 | Parallel tests publication and subscription might fail due to concurrent tuple update |