From: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Sebastien Lemieux <slemieux(at)elitra(dot)com>, Postgresql-performance <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: How to efficiently duplicate a whole schema? |
Date: | 2003-08-06 19:09:47 |
Message-ID: | Pine.LNX.4.33.0308061307560.16245-100000@css120.ihs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Wed, 6 Aug 2003, Tom Lane wrote:
> Sebastien Lemieux <slemieux(at)elitra(dot)com> writes:
> > All the time is taken at the commit of both transaction.
>
> Sounds like the culprit is foreign-key checks.
>
> One obvious question is whether you have your foreign keys set up
> efficiently in the first place. As a rule, the referenced and
> referencing columns should have identical datatypes and both should
> be indexed. (PG will often let you create foreign key constraints
> that don't meet these rules ... but performance will suffer.)
Is this one of those things that should spit out a NOTICE when it happens?
I.e. when a table is created with a references and uses a different type
than the parent, would it be a good idea to issue a "NOTICE: parent and
child fields are not of the same type"
From | Date | Subject | |
---|---|---|---|
Next Message | Nick Fankhauser | 2003-08-06 19:09:48 | Re: How to efficiently duplicate a whole schema? |
Previous Message | Sebastien Lemieux | 2003-08-06 18:56:14 | How to efficiently duplicate a whole schema? |