From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
---|---|
To: | Serge Rielau <serge(at)rielau(dot)com> |
Cc: | Vitaly Burovoy <vitaly(dot)burovoy(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)anarazel(dot)de>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Fast AT ADD COLUMN with DEFAULTs |
Date: | 2016-10-06 11:19:48 |
Message-ID: | CANP8+jK24gb=Ti_L2TZUenmQv8XQvya1Vz+zfmivDY6_mYLN1g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 6 October 2016 at 04:43, Serge Rielau <serge(at)rielau(dot)com> wrote:
>>> Or should I compose some sort of a design document?
Having read this thread, I'm a little unclear as to what you're
writing now, though there's definitely good ideas here.
I think it would be beneficial to write up a single coherent
description of this, including behaviour and a small sketch of
implementation, just so everyone knows what this is. No design doc,
but a summary.
It would be very useful to be able to do this...
ALTER TABLE foo ADD last_updated_timestamp timestamp default current_timestamp
so that it generates a constant value and stores that for all prior
rows, but then generates a new value for future rows.
Which makes me think we should call this missing_value or absent_value
so its clear that it is not a "default" it is the value we use for
rows that do not have any value stored for them.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Petr Jelinek | 2016-10-06 12:12:03 | Re: autonomous transactions |
Previous Message | Amit Langote | 2016-10-06 11:17:47 | Re: postgres_fdw : altering foreign table not invalidating prepare statement execution plan. |