| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Csaba Nagy <ncslists(at)googlemail(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: ALTER TABLE ... REPLACE WITH |
| Date: | 2010-12-15 15:50:13 |
| Message-ID: | 1292428213.1193.242.camel@ebony |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 2010-12-15 at 12:17 +0100, Csaba Nagy wrote:
> But one problem would be when the replaced table is the _parent_ for a
> foreign key relationship. I don't think you can have that constraint
> pre-verified on the replacement table and simply replacing the content
> could leave the child relations with orphans.
Good point.
The only sensible way to handle this is by putting the FK checks into
check pending state (as discussed on a different thread).
We would probably need to disallow FKs with DELETE or UPDATE CASCADE
since it would be difficult to execute those.
--
Simon Riggs http://www.2ndQuadrant.com/books/
PostgreSQL Development, 24x7 Support, Training and Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Florian Pflug | 2010-12-15 15:52:28 | Re: hstores in pl/python |
| Previous Message | Simon Riggs | 2010-12-15 15:47:04 | Re: ALTER TABLE ... REPLACE WITH |