Message-ID: <4847A9CC.2010406@archonet.com>
Date: Thu, 05 Jun 2008 09:54:36 +0100
From: Richard Huxton <dev@archonet.com>
User-Agent: Thunderbird 2.0.0.14 (X11/20080421)
MIME-Version: 1.0
To: Simon Riggs <simon@2ndquadrant.com>
CC: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: pg_dump restore time and Foreign Keys
References: <1212647003.19964.19.camel@ebony.site>
In-Reply-To: <1212647003.19964.19.camel@ebony.site>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Simon Riggs wrote:
> 
> If we had a way of pg_dump passing on the information that the test
> already passes, we would be able to skip the checks.
> 
> Proposal:
> 
> * Introduce a new mode for ALTER TABLE ADD FOREIGN KEY [WITHOUT CHECK];

> * Have pg_dump write the new syntax into its dumps, when both the source
> and target table are dumped in same I've been known to manually tweak dumps before now. I can see me 
forgetting this.

What about pg_dump writing out a row-count and MD5 of the rows in the 
COPY (just a textual calculation). Iff the restore checksum matches the 
dump checksum for both tables then the foreign-keys can be skipped.

If the restore checksum doesn't match the dump then it can issue a 
warning, but continue and run the full fkey check.

-- 
   Richard Huxton
   Archonet Ltd