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

Re: Check constraints on partition parents only?

From: Nikhil Sontakke <nikhil(dot)sontakke(at)enterprisedb(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Nikhil Sontakke <nikkhils(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Alex Hunsaker <badalex(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Jerry Sievers <gsievers19(at)comcast(dot)net>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Check constraints on partition parents only?
Date: 2011-07-29 13:49:52
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
> > Yeah, I have already hacked it a bit. This constraint now needs to be
> > spit out later as an ALTER command with ONLY attached to it
> > appropriately. Earlier all CHECK constraints were generally emitted as
> > part of the table definition itself.
> IIRC, there's already support for splitting out a constraint that way,
> in order to deal with circular dependencies.  You just need to treat
> this as an additional reason for splitting.
Yeah, I have indeed followed the existing separate printing logic for "ONLY"
constraints. Had to make the table dependent on this constraint to print the
constraint *after* the table definition.


In response to

pgsql-hackers by date

Next:From: Kevin GrittnerDate: 2011-07-29 13:52:58
Subject: Re: cheaper snapshots
Previous:From: Nikhil SontakkeDate: 2011-07-29 13:47:52
Subject: Re: Check constraints on partition parents only?

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group