diff options
| author | Peter Eisentraut <peter@eisentraut.org> | 2024-02-09 07:57:31 +0100 |
|---|---|---|
| committer | Peter Eisentraut <peter@eisentraut.org> | 2024-02-09 08:15:27 +0100 |
| commit | d17a3a4c6a34f61a3d4d9faa7a70c14d8d0c0ffb (patch) | |
| tree | 448c4b51e57740cc0aede21b21e8210f259df1f9 /src/backend/executor/execParallel.c | |
| parent | 27c3a41f3cfbfc3ab471fd85b4885d39f7c42ae6 (diff) | |
| download | postgresql-d17a3a4c6a34f61a3d4d9faa7a70c14d8d0c0ffb.tar.gz postgresql-d17a3a4c6a34f61a3d4d9faa7a70c14d8d0c0ffb.zip | |
Fix propagation of persistence to sequences in ALTER TABLE / ADD COLUMN
Fix for 344d62fb9a9: That commit 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. The latter would
always create the sequence as logged (default), independent of the
persistence setting of the table. This is fixed here.
Note: It is allowed to change the persistence of identity sequences
directly using ALTER SEQUENCE. So mistakes in existing databases can
be fixed manually.
Reviewed-by: Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>
Discussion: https://www.postgresql.org/message-id/flat/c4b6e2ed-bcdf-4ea7-965f-e49761094827%40eisentraut.org
Diffstat (limited to 'src/backend/executor/execParallel.c')
0 files changed, 0 insertions, 0 deletions