From: | PG Doc comments form <noreply(at)postgresql(dot)org> |
---|---|
To: | pgsql-docs(at)lists(dot)postgresql(dot)org |
Cc: | t(at)gobet(dot)ar |
Subject: | ALTER TABLE atomicity with sub-commands |
Date: | 2024-04-02 14:40:24 |
Message-ID: | 171206882423.679.7317080738034337679@wrigleys.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/15/sql-altertable.html
Description:
Hello dear PostgreSQL family,
It is not entirely clear (to me) that ALTER TABLE statements with
comma-separated sub-commands are atomic. Despite of saying "perform X
actions in one operation" in one of the examples, it is not explicitly said
that the operation will be rolled back if one of the sub-commands fails.
From the examples, we have:
ALTER TABLE distributors
ALTER COLUMN address TYPE varchar(80),
ALTER COLUMN name TYPE varchar(100);
Will the `address` column type change rollback if the `ALTER COLUMN name
TYPE varchar(100)` subcommand fails?
Currently reading the docs for version 15.
Many thanks :)
From | Date | Subject | |
---|---|---|---|
Next Message | Erik Wienhold | 2024-04-02 21:11:56 | Re: ALTER TABLE atomicity with sub-commands |
Previous Message | Noah Misch | 2024-03-31 06:16:42 | Re: CREATE ROLE inheritance details |