Re: Documentation fix for adding a column with a default value
Ian Barwick <ian.barwick@2ndquadrant.com>
From: Ian Barwick <ian.barwick@2ndquadrant.com>
To: Daniel Gustafsson <daniel@yesql.se>,
"Daniel Westermann (DWE)" <daniel.westermann@dbi-services.com>
Cc: "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2019-07-19T00:04:03Z
Lists: pgsql-hackers
On 7/19/19 12:51 AM, Daniel Gustafsson wrote: >> On 18 Jul 2019, at 17:46, Daniel Westermann (DWE) <daniel.westermann@dbi-services.com> wrote: >> >>>> The suggested change pares down the "Tip" to more of a brief "Note", which IMHO is a bit >>>> terse for that section of the documentation (which has more of a tutorial character), >>>> and the contents of the original tip basically still apply for volatile default values >>>> anyway. >>>> >>>> I've attached another suggestion for rewording this which should also make the >>>> mechanics of the operation a little clearer. >> >>> Thank you, that better explains it. Looks good to me. >> >> Shouldn't we add that to the current commit fest? > > The current commitfest is closed for new additions, but please add it to the > next one (2019-09) and it will be picked up then. To me it looks like a minor documentation correction to fix an omission from a patch already in PostgreSQL. Regards Ian Barwick -- Ian Barwick https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services
Commits
-
Doc: clarify when table rewrites happen with column addition and DEFAULT
- 80aa66392ec8 11.5 landed
- b990cc38dc64 12.0 landed
- 1300fa66b2f3 13.0 landed