Tom Lane wrote:
> Jesper Krogh <jesper(at)krogh(dot)cc> writes:
>> The tables are running a "home-made" timetravelling feature where a
>> contraint on the table implements the foreing keys on the table.
> You mean you have check constraints that do selects on other tables?
Yes. We do.. we have to .. in order to perserve the foreing-keys.
What we have in short is:
Added two timestamps on each columns, starttime,endtime. When endtime is
"null" the record is "current" and a view exposes this from the table.
The foreing keys are then implemented using contraints that look up the
id in the foreing table and ensures that there is a record where the
endtime is null present
> You have just found out (one reason) why that's a bad idea.
Do you have any other reasons?
>> How can I instruct pg_dumpall to turn off these constriants during
> Drop the constraints in the source database.
That would be my workaround for the problem. But isn't it somehow
desirable that pg_dumpall | psql "allways" would work?
Jesper Krogh, jesper(at)krogh(dot)cc
In response to
pgsql-admin by date
|Next:||From: Alvaro Herrera||Date: 2007-10-17 21:56:53|
|Subject: Re: postgresql para windows para 64 bits|
|Previous:||From: Tom Lane||Date: 2007-10-17 16:10:34|
|Subject: Re: Upgrade time, dump+restore trouble. |