Re: AW: Proposal: More flexible backup/restore via pg_dump - Mailing list pgsql-hackers

From Giles Lean
Subject Re: AW: Proposal: More flexible backup/restore via pg_dump
Date
Msg-id 5054.962146132@nemeton.com.au
Whole thread Raw
In response to Re: AW: Proposal: More flexible backup/restore via pg_dump  (Philip Warner <pjw@rhyme.com.au>)
Responses Re: AW: Proposal: More flexible backup/restore via pg_dump  (Philip Warner <pjw@rhyme.com.au>)
List pgsql-hackers
> I don't suppose anyone knows of a way of telling if a file handle supports
> seek?

The traditional method is to call lseek() and see what happens.

> Part of the motivation for this utility was to allow DBAs to fix the
> ordering at restore time, but otherwise I totally agree. Unfortunately I
> don't think the RI checks can be delayed at this stage - can they? 

The current pg_dump handles the data and then adds the constraints.

Otherwise there are "chicken and egg" problems where two tables have
mutual RI constraints.  Even at the tuple level two tuples can be
mutually dependent.

Regards,

Giles




pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Please help cache lookup failed
Next
From: Hiroshi Inoue
Date:
Subject: Re: Big 7.1 open items