| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| 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:19:45 |
| Message-ID: | 23306.1295565585@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Thu, Jan 20, 2011 at 4:24 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> 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.
Well, if you want to preserve dependencies, you can *not* just blindly
substitute an incompatible table. You must ensure that views and
foreign keys referencing the table are still valid. So I'm not sure
where anybody got the idea that an implementation that fails to check
all that is even worth presenting.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2011-01-20 23:22:49 | Re: SSI and Hot Standby |
| Previous Message | Noah Misch | 2011-01-20 23:19:20 | Re: ALTER TABLE ... REPLACE WITH |