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
