Re: Constraints & pg_dump

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Constraints & pg_dump
Date: 2004-03-17 12:23:59
Message-ID: 4058435F.2030009@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:

>Our present handling of CHECK constraints cannot reasonably be
>thought to support anything but row-local constraints. If they're using
>a function to make an end-run around the check that prohibits subselects
>in CHECK constraints, then their problems are much more serious than
>whether pg_dump dumps the database in an order that manages to avoid
>failure. That kind of constraint just plain does not work, because it
>won't get rechecked when the implicitly referenced rows change.
>
>

Ouch. Two days ago I saw someone on IRC (I think from this list)
actually advising someone to use this end-run. Maybe we need to beef up
the docs on this point?

cheers

andrew

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message BARTKO, Zoltan 2004-03-17 14:01:21 Re: Doxygen?
Previous Message Fabien COELHO 2004-03-17 09:19:57 Re: Further thoughts about warning for costly FK checks