| From: | Alexander Lakhin <exclusion(at)gmail(dot)com> |
|---|---|
| To: | Noah Misch <noah(at)leadboat(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org, Smolkin Grigory <smallkeen(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz> |
| Subject: | Re: race condition in pg_class |
| Date: | 2024-07-03 03:00:00 |
| Message-ID: | a295b499-dcab-6a99-c06e-01cf60593344@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hello Noah,
29.06.2024 05:42, Noah Misch wrote:
> Good point, any effort on (2) would be wasted once the fixes get certified. I
> pushed (1). I'm attaching the rebased fix patches.
Please look at a new anomaly, introduced by inplace110-successors-v5.patch:
CREATE TABLE t (i int) PARTITION BY LIST(i);
CREATE TABLE p1 (i int);
ALTER TABLE t ATTACH PARTITION p1 FOR VALUES IN (1);
ALTER TABLE t DETACH PARTITION p1;
ANALYZE t;
triggers unexpected
ERROR: tuple to be updated was already modified by an operation triggered by the current command
Best regards,
Alexander
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zhijie Hou (Fujitsu) | 2024-07-03 03:00:50 | RE: Conflict detection and logging in logical replication |
| Previous Message | Peter Smith | 2024-07-03 02:54:18 | Re: Logical Replication of sequences |