Re: Sometimes pg_dump generates dump which is not restorable

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: dmitry(at)koterov(dot)ru
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Sometimes pg_dump generates dump which is not restorable
Date: 2008-11-14 16:25:39
Message-ID: 27805.1226679939@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Dmitry Koterov" <dmitry(at)koterov(dot)ru> writes:
> Thank you for a possible solution.
> But what about the database which exists and works correctly (and conforms
> all the standards from the documentation), but dump+restore sequence is
> failed for it? Does it mean that pg_dump should be improved to pass
> dump+restore sequence?

No matter what pg_dump does, it can never guarantee that a non-immutable
check constraint will still pass at restore time ... and that's
basically what you've got, if the check function is
search-path-sensitive.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2008-11-14 16:36:31 Re: Updates of SE-PostgreSQL 8.4devel patches (r1197)
Previous Message Robert Haas 2008-11-14 16:21:20 Re: CREATE AGGREGATE disallows STYPE = internal