| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Noah Misch <noah(at)leadboat(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org, heikki(dot)linnakangas(at)enterprisedb(dot)com |
| Subject: | Re: ALTER TABLE ... REPLACE WITH |
| Date: | 2011-01-20 23:07:59 |
| Message-ID: | AANLkTinEcHpENHNaohcthaz3SRBZBqJk51yWhGrtboAE@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Jan 20, 2011 at 4:24 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Noah Misch <noah(at)leadboat(dot)com> writes:
>> Heikki's suggestion seemed straightforward, so much so that I couldn't figure
>> why nobody had done it. That would usually mean I'm missing something.
>
> If you're willing to substitute an incompatible table, it's not clear
> why you don't just do
>
> begin;
> drop table t;
> alter table t_new rename to t;
> commit;
Because the whole source of this problem is dependency hell.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Farina | 2011-01-20 23:10:19 | Re: One Role, Two Passwords |
| Previous Message | Andrew Dunstan | 2011-01-20 22:45:58 | Re: One Role, Two Passwords |