aboutsummaryrefslogtreecommitdiff
path: root/src/backend/parser/parse_merge.c
diff options
context:
space:
mode:
authorPeter Eisentraut <peter@eisentraut.org>2024-02-09 07:57:31 +0100
committerPeter Eisentraut <peter@eisentraut.org>2024-02-09 08:09:59 +0100
commit86d2b434c9a3520a10db4feae236b74452d3d157 (patch)
tree7d54f9fdc5a51b5e5767e191154f2a51c41177d0 /src/backend/parser/parse_merge.c
parente13205a5e4ad0fb75110a25f81654511303566f8 (diff)
downloadpostgresql-86d2b434c9a3520a10db4feae236b74452d3d157.tar.gz
postgresql-86d2b434c9a3520a10db4feae236b74452d3d157.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/parser/parse_merge.c')
0 files changed, 0 insertions, 0 deletions