| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Greg Stark <gsstark(at)mit(dot)edu>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: ADD/DROP INHERITS |
| Date: | 2006-06-08 21:21:47 |
| Message-ID: | 448894EB.6030304@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Simon Riggs wrote:
> Based on the test case Tom shows, I think we need to enforce that ADD
> INHERITS will barf if the columns are not in exactly the order they
> would have been in if we add done a CREATE ... INHERITS followed by a
> DROP INHERITS. That wouldn't be a problem if we just say to people, if
> you want to create a new partition do:
>
> CREATE TABLE new_child ... LIKE child;
>
> then later
>
> ALTER TABLE new_partition ADD INHERITS parent;
>
>
This seems like a very reasonable restriction. I imagine in the most
common case at least they will be exact clones.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2006-06-08 21:23:04 | Re: ADD/DROP INHERITS |
| Previous Message | Tom Lane | 2006-06-08 21:21:26 | Re: That EXPLAIN ANALYZE patch still needs work |