| From: | Vitaly Burovoy <vitaly(dot)burovoy(at)gmail(dot)com> |
|---|---|
| To: | Serge Rielau <serge(at)rielau(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Simon Riggs <simon(at)2ndquadrant(dot)com>, 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 16:38:50 |
| Message-ID: | CAKOSWNkSz97-rvNX9+=isfqrNHrkrk+ABn7ANngxJ0f4Dj9F7g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 10/6/16, Vitaly Burovoy <vitaly(dot)burovoy(at)gmail(dot)com> wrote:
> Ough. I made a mistake about pg_attribute because I forgot about the
> pg_attrdef.
> If we do not merge these tables, the pg_attrdef is the best place to
> store evaluated expression as a constant the same way defaults are
> stored in adbin.
Oops. While I was writing the previous email, Tom explained necessity
of the pg_attrdef.
With that explanation it is obvious that I was wrong and a value for
pre-existing rows should be in a new column in the pg_attribute.
All the other thoughts from my previous email stand good.
--
Best regards,
Vitaly Burovoy
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Serge Rielau | 2016-10-06 16:39:05 | Re: Fast AT ADD COLUMN with DEFAULTs |
| Previous Message | Vitaly Burovoy | 2016-10-06 16:26:10 | Re: Fast AT ADD COLUMN with DEFAULTs |