Re: Documentation fix for adding a column with a default value - Mailing list pgsql-hackers

From Ian Barwick
Subject Re: Documentation fix for adding a column with a default value
Date
Msg-id 7c252f52-4f39-e2d3-ea38-1e7643aacf0b@2ndquadrant.com
Whole thread Raw
In response to Re: Documentation fix for adding a column with a default value  (Daniel Gustafsson <daniel@yesql.se>)
Responses Re: Documentation fix for adding a column with a default value  (Michael Paquier <michael@paquier.xyz>)
List 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



pgsql-hackers by date:

Previous
From: Mike Palmiotto
Date:
Subject: Re: sepgsql seems rather thoroughly broken on Fedora 30
Next
From: Jeff Davis
Date:
Subject: Re: Bad canonicalization for dateranges with 'infinity' bounds