Re: pg_restore and create FK without verification check

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: ow <oneway_111(at)yahoo(dot)com>
Cc: Andreas Pflug <pgadmin(at)pse-consulting(dot)de>, Hannu Krosing <hannu(at)tm(dot)ee>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_restore and create FK without verification check
Date: 2003-11-26 21:33:19
Message-ID: 17867.1069882399@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

ow <oneway_111(at)yahoo(dot)com> writes:
> --- Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Quite honestly, I think they should check their foreign keys.

> Generally speaking, I agree. The problem is that verification of FK
> constraint(s) may take too long, depending on the size of the db and other
> conditions. In my case, on test data, it takes about 1 hour to create tables
> and copy the data, then about 40 min to create indexes, then 4.5 hours to
> create one (1) FK constraint.

If you're seeing this on 7.4, I'd like to see the details of the exact
commands being issued. If it's not 7.4, it's not a relevant
measurement.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2003-11-26 22:06:47 Re: Limiting factors of pg_largeobject
Previous Message Neil Conway 2003-11-26 21:10:01 Re: detecting poor query plans