Skip site navigation (1) Skip section navigation (2)

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search for
  Advanced Search

Re: error-free disabling of individual child partition


  • From: Simon Riggs <simon(at)2ndquadrant(dot)com>
  • To: Zeugswetter Andreas DCP SD <ZeugswetterA(at)spardat(dot)at>
  • Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, April Lorenzen <outboundindex(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
  • Subject: Re: error-free disabling of individual child partition
  • Date: Tue, 23 May 2006 10:51:44 +0100
  • Message-id: <1148377904(dot)2646(dot)795(dot)camel(at)localhost(dot)localdomain>

On Tue, 2006-05-23 at 09:49 +0200, Zeugswetter Andreas DCP SD wrote:
> > > table of another table. I propose a TODO item to allow this:
> > >
> > > 	ALTER TABLE childN INHERITS ( parent1, ... );
> 
> > > We don't need a disinherit do we?
> 
> I propose: ALTER TABLE childN INHERITS ();
> Thus I also think, that the list should be complete, and is not an
> addition 
> to existing inheritance.

Sounds good; an absolute rather than a relative approach. Avoids new
keywords.

Implementation is simpler too:
- check that we have all required merged attributes (if any)
- remove any inheritance that isn't on the list

If the table is already INHERITS (x) and we specify INHERITS (x) then
its a no-op that returns success.
 
> > O, yes, I think we do. I can imagine that the ability to swap a table 
> 
> Agreed. Simon, were you testing how many ppl read to the end :-)

Just seeing who cared. DROP TABLE removes inheritance too, in a Keyser
Soze manner.

-- 
  Simon Riggs             
  EnterpriseDB   http://www.enterprisedb.com




Home | Main Index | Thread Index

Privacy Policy | PostgreSQL Archives hosted by Command Prompt, Inc. | Designed by tinysofa
Copyright © 1996 – 2008 PostgreSQL Global Development Group