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-17 09:08:36
Message-ID: DB6PR0902MB21842DC72DF2F311A7A36820D2C90@DB6PR0902MB2184.eurprd09.prod.outlook.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


>> Seems the first mail didn't make it ...

>Actually it did, I was about to reply to it :)
>
>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.

Regards
Daniel

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Langote 2019-07-17 09:08:48 Re: CVE-2017-7484-induced bugs, or, btree cmp functions are not leakproof?
Previous Message Ibrar Ahmed 2019-07-17 08:44:44 Re: block-level incremental backup