Re: Fw: Documentation fix for adding a column with a default value

From: "Daniel Westermann (DWE)" <daniel(dot)westermann(at)dbi-services(dot)com>
To: Ian Barwick <ian(dot)barwick(at)2ndquadrant(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Fw: Documentation fix for adding a column with a default value
Date: 2019-07-18 15:46:00
Message-ID: DB6PR0902MB21842F334B22C5C7FAEF04ACD2C80@DB6PR0902MB2184.eurprd09.prod.outlook.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>>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?

Regards
Daniel

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Daniel Gustafsson 2019-07-18 15:51:26 Re: Documentation fix for adding a column with a default value
Previous Message Tom Lane 2019-07-18 15:42:12 Re: buildfarm's typedefs list has gone completely nutso