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:09:22 +0100 |
| commit | 6743c5ae64e3c957ef8bd4f8a0daa2ba9959b0b3 (patch) | |
| tree | 4a92063a9a313f4ce70def1893ac6d02a8b7656b /src/backend/utils/adt/jsonpath_exec.c | |
| parent | 3c44746fdb5d5603f6bc4645c78bca6c702fc920 (diff) | |
| download | postgresql-6743c5ae64e3c957ef8bd4f8a0daa2ba9959b0b3.tar.gz postgresql-6743c5ae64e3c957ef8bd4f8a0daa2ba9959b0b3.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/utils/adt/jsonpath_exec.c')
0 files changed, 0 insertions, 0 deletions