On Fri, Aug 24, 2012 at 10:38 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Chris Travers <chris(at)metatrontech(dot)com> writes:
>> Table inheritance would be easier if there was a way to declare a
>> constraint such that it prevents insert for some rows on the parent
>> but not for a child and/or vice versa.
> FWIW, 9.2 adds support for constraints that only apply to the named
> table and don't get inherited to children. I think use of such
> constraints is probably better design than mucking around with tableoid,
> even if we were to make that work.
Maybe, but in that case shouldn't referencing a system column chuck an error?
The Enterprise PostgreSQL Company
In response to
pgsql-bugs by date
|Next:||From: Tom Lane||Date: 2012-08-27 20:34:01|
|Subject: Re: Minor inheritance/check bug: Inconsistent behavior|
|Previous:||From: Tom Lane||Date: 2012-08-27 19:31:08|
|Subject: Re: BUG #7507: pg_restore silently fails when restoring a db with the --create flag and no user.|