pg_dump and restore problem with function as DEFAULT-Constraint

From: Markus Schulz <msc(at)antzsystem(dot)de>
To: pgsql-general(at)postgresql(dot)org
Subject: pg_dump and restore problem with function as DEFAULT-Constraint
Date: 2007-02-27 16:44:06
Message-ID: 200702271744.06730.msc@antzsystem.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hello,

i have some trouble with dumping and restoring a database with
postgresql 7.4.7-6sarge4 (debian sarge).

Some tables have plpgsql-functions as DEFAULT contraints. But these
functions are dumped after the CREATE TABLE command. Now these tables
can't be created on restore.

If i'm dumping only structure and import twice in a new and empty
database (this works), i can't restore the data-only dump. Cause in the
data-only dump the table order was wrong in respect to FOREIGN KEY
constraints and the constraints are now active (instead of a full-dump,
where constraints will be created after data was inserted).

Why DEFAULT (and NOT NULL) constraints would'nt be added after data
insertion? (like Primary-Key and Foreign-Key)

What can i do to enforce the order of plpgsql functions prior to all
table structures?

--
Markus Schulz - msc(at)antzsystem(dot)de

Responses

Browse pgsql-general by date

  From Date Subject
Next Message A. Kretschmer 2007-02-27 17:28:51 Re: pg_dump and restore problem with function as DEFAULT-Constraint
Previous Message David Gagnon 2007-02-27 16:35:33 Re: select ARRAY[1, 4, 3] @> ARRAY[3, 1] gives ERROR: operator does not exist: integer[] @> integer[] ???