From: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us>, Peter Geoghegan <pg(at)bowt(dot)ie> |
Cc: | Teodor Sigaev <teodor(at)sigaev(dot)ru>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Postgres 11 release notes |
Date: | 2018-05-14 11:47:54 |
Message-ID: | 6a28a9c2-d1aa-966c-e1f4-848750de2189@2ndQuadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-www |
On 05/12/2018 08:47 PM, Bruce Momjian wrote:
> On Sat, May 12, 2018 at 01:22:55PM -0700, Peter Geoghegan wrote:
>> On Fri, May 11, 2018 at 2:06 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
>>> Done and URL updated.
>> I have some feedback on "Allow NOT NULL to be added to columns without
>> requiring a table rewrite". I suggest that this be phrased as "Avoid a
>> table rewrite when ALTER TABLE ADD COLUMN sets a default value for a
>> column". Referencing the fact that Postgres was previously able to do
>> this with a NULL default doesn't seem to add anything.
> Agreed, done:
>
> Allow <command>ALTER TABLE</command> to add a non-null default
> column without a table rewrite (Andrew Dunstan, Serge Rielau)
>
I think "a column with a non-null default" would be a bit clearer than
"a non-null default column".
cheers
andrew
--
Andrew Dunstan https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Dilip Kumar | 2018-05-14 12:04:54 | Re: Postgres 11 release notes |
Previous Message | Andrew Dunstan | 2018-05-14 11:36:06 | Re: Allow COPY's 'text' format to output a header |
From | Date | Subject | |
---|---|---|---|
Next Message | Dilip Kumar | 2018-05-14 12:04:54 | Re: Postgres 11 release notes |
Previous Message | David Steele | 2018-05-14 11:10:18 | Re: Postgres 11 release notes |