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

From: Ian Barwick <ian(dot)barwick(at)2ndquadrant(dot)com>
To: Daniel Gustafsson <daniel(at)yesql(dot)se>, "Daniel Westermann (DWE)" <daniel(dot)westermann(at)dbi-services(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Documentation fix for adding a column with a default value
Date: 2019-07-19 00:04:03
Message-ID: 7c252f52-4f39-e2d3-ea38-1e7643aacf0b@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 7/19/19 12:51 AM, Daniel Gustafsson wrote:
>> On 18 Jul 2019, at 17:46, Daniel Westermann (DWE) <daniel(dot)westermann(at)dbi-services(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Davis 2019-07-19 00:17:03 Re: Bad canonicalization for dateranges with 'infinity' bounds
Previous Message Mike Palmiotto 2019-07-18 23:23:08 Re: sepgsql seems rather thoroughly broken on Fedora 30