On Wed, Jul 27, 2011 at 14:08, Tom Lane <t...@sss.pgh.pa.us> wrote: > Yeah. If we're going to allow this then we should just have a concept > of a non-inherited constraint, full stop. This might just be a matter > of removing the error thrown in ATAddCheckConstraint, but I'd be worried > about whether pg_dump will handle the case correctly, what happens when > a new child is added later, etc etc.
[ For those who missed it ] pg_dump getting things wrong was a big reason to disallow ONLYconstraints. That is pg_dump did not treat ONLY constraints correctly, it always tried to stick them on the parent table: http://archives.postgresql.org/pgsql-bugs/2007-04/msg00026.php I for example had some backups that had to be manually fixed (by removing constraints) to get them to import. I would wager the mentioned clients that have been doing this have broken backups as well :-( Now that we have coninhcnt, conislocal etc... we can probably support ONLY. But I agree with Robert it's probably a bit more than an afternoon to crank out :-) -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
