Re: Fix propagation of persistence to sequences in ALTER TABLE / ADD COLUMN
Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>
From: Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>
To: Peter Eisentraut <peter@eisentraut.org>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2024-02-08T06:04:47Z
Lists: pgsql-hackers
Attachments
- 0001-Fix-propagation-of-persistence-to-sequences-20240208.patch (text/x-patch) patch 0001
- 0002-Additional-tests-20240208.patch (text/x-patch) patch 0002
On Mon, Feb 5, 2024 at 9:21 PM Peter Eisentraut <peter@eisentraut.org> wrote: > > Commit 344d62fb9a9 (2022) introduced unlogged sequences and made it so > that identity/serial sequences automatically get the persistence level > of their owning table. But this works only for CREATE TABLE and not for > ALTER TABLE / ADD COLUMN. This patch fixes that. (should be > backpatched to 15, 16) The patch looks ok. + seqstmt->sequence->relpersistence = cxt->rel ? cxt->rel->rd_rel->relpersistence : cxt->relation->relpersistence; + This condition looks consistent with the other places in the code around line 435, 498. But I was worried that cxt->rel may not get latest relpersistence if the ALTER TABLE changes persistence as well. Added a test (0002) which shows that ctx->rel has up-to-date relpersistence. Also added a few other tests. Feel free to include/reject them while committing. 0001 - same as your patch 0002 - additional tests -- Best Wishes, Ashutosh Bapat
Commits
-
Fix propagation of persistence to sequences in ALTER TABLE / ADD COLUMN
- d17a3a4c6a34 15.7 landed
- 86d2b434c9a3 16.3 landed
- 6743c5ae64e3 17.0 landed
-
Unlogged sequences
- 344d62fb9a97 15.0 cited