| From: | Masahiro Ikeda <ikedamsh(at)oss(dot)nttdata(dot)com> |
|---|---|
| To: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Doc: fix the rewrite condition when executing ALTER TABLE ADD COLUMN |
| Date: | 2024-12-03 08:13:24 |
| Message-ID: | 00e6eb5f5c793b8ef722252c7a519c9a@oss.nttdata.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
The documentation seems to overlook the rewrite condition
when executing ALTER TABLE ADD COLUMN.
The current document states that a volatile DEFAULT will
trigger a rewrite of the table and its indexes. However, the
table and its indexes will also be rewritten when an IDENTITY
column is added, or when a column with a domain data type that
has constraints is added.
What do you think?
Regards,
--
Masahiro Ikeda
NTT DATA CORPORATION
| Attachment | Content-Type | Size |
|---|---|---|
| test.sql | text/plain | 1.6 KB |
| test.out | text/plain | 3.5 KB |
| v1-0001-Doc-fix-the-rewrite-condition-when-executing-ALTE.patch | text/x-diff | 3.1 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2024-12-03 08:15:18 | Re: Don't overwrite scan key in systable_beginscan() |
| Previous Message | Jeff Davis | 2024-12-03 07:58:36 | Re: Collation & ctype method table, and extension hooks |