From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
Cc: | April Lorenzen <outboundindex(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: error-free disabling of individual child partition |
Date: | 2006-05-22 20:37:59 |
Message-ID: | 44722127.7040108@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Simon Riggs wrote:
>
> There is not currently any way to make an existing table become a child
> table of another table. I propose a TODO item to allow this:
>
> ALTER TABLE childN INHERITS ( parent1, ... );
>
> This would only succeed if all of the columns that would have been
> inherited from all parent tables already exist with the same name and
> datatype, nullability and default values. Additional columns would be
> allowed in the child table.
>
> This would also allow you to use CREATE TABLE AS SELECT and then move
> that table underneath a parent.
>
> We don't need a disinherit do we?
>
>
O, yes, I think we do. I can imagine that the ability to swap a table
out of a set without deleting it could be very useful (e.g. you might
move it in as a child of an archive table). These two would add markedly
to the usefulness of inheritance as a partitioning mechanism.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2006-05-22 20:39:26 | Re: Porting MSSQL to PGSQL (Was: [OT] MySQL is bad, but THIS |
Previous Message | Simon Riggs | 2006-05-22 20:19:03 | Re: error-free disabling of individual child partition |