So you look up other tables in a
CHECK constraints are supposed to run
IMMUTABLE checks. What passes OK for a row at one time should pass OK at any time. That's how
CHECK constraints are defined in the SQL standard. That's also the reason for this restriction in the manual:
CHECK expressions cannot contain subqueries nor refer to
variables other than columns of the current row.
Still, expressions in
CHECK constraints are allowed to use functions, even user-defined functions. Those should be
IMMUTABLE, but Postgres does not currently enforce this. According to this related discussion on pgsql-hackers, one reason is to allow references to the current time, which is not
IMMUTABLE by nature.
But you are looking up rows of another table, which is completely in violation of how
CHECK constraints are supposed to work. I am not surprised that
pg_dump fails to provide for this.
Move your check in another table to a trigger (which is the right tool), and it should work with modern versions of Postgres.
PostgreSQL 9.2 or later
While the above is true for any version of Postgres, several tools have been introduced with Postgres 9.2 to help with your situation:
A simple solution would be to dump the db without data for the violating table with:
Then append just the data for this table at the end of the dump with:
But complications with other constraints on the same table might ensue. There is an even better solution:
Up to Postgres 9.1, the
NOT VALID modifier was only available for FK constraints. This was extended to
CHECK constraints in Postgres 9.2. The manual:
If the constraint is marked
NOT VALID, the potentially-lengthy
initial check to verify that all rows in the table satisfy the
constraint is skipped. The constraint will still be enforced against
subsequent inserts or updates [...]
A plain Postgres dump file consists of three "sections":
Postgres 9.2 also introduced an option to dump sections separately with
-- section=sectionname, but that's not helping with the problem at hand.
Here is where it gets interesting. The manual:
Post-data items include definitions of indexes, triggers, rules, and
constraints other than validated check constraints. Pre-data items
include all other data definition items.
Bold emphasis mine.
You can change the offending
CHECK constraint to
NOT VALID, which moves the constraint to the
post-data section. Drop and recreate:
ALTER TABLE a
DROP CONSTRAINT a_constr_1
, ADD CONSTRAINT a_constr_1 CHECK (fail_if_b_empty()) NOT VALID;
A single statement is fastest and rules out race conditions with concurrent transactions. (Two commands in a single transaction would work, too.)
This should solve your problem. You can even leave the constraint in that state, since that better reflects what it actually does: check new rows, but give no guarantees for existing data. There is nothing wrong with a
NOT VALID check constraint. If you prefer, you can validate it later:
ALTER TABLE a VALIDATE CONSTRAINT a_constr_1;
But then you are back to the status quo ante.