From: CG <cgg007@yahoo.com>
To: pgsql-admin@postgresql.org
Subject: WARNING: foreign key constraint will require costly sequential scans during pg_restore
Date: Wed, 22 Feb 2006 07:26:11 -0800 (PST)
Message-ID: <20060222152611.13188.qmail@web32515.mail.mud.yahoo.com> (raw)
Hey Tom: Thanks for the fix for allowing a the restore of dumps that have
cross-schema references to custom operators or operator classes. It did the
trick!
I have another non-critical issue which may or may not be related...
pg_restore: WARNING: foreign key constraint "luuid_fkey" will require costly
sequential scans
DETAIL: Key columns "luuid" and "luuid" are of different types:
public.uniqueidentifier and public.uniqueidentifier.
First, this occurrs during a pg_restore, so the database hasn't been
analyzed... Second, the warning doesn't block the FK from being created. I also
doubt that with the proper indexes that it would create costly sequential
scans, but it's hard to tell, since there's a ton of things going on during
inserts to that table only one of which is FK constraint checking.
So, my real question is should I ignore the warning, or is it an indicator of a
problem?
CG
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: cgg007@yahoo.com
Subject: Re: WARNING: foreign key constraint will require costly sequential scans during pg_restore
In-Reply-To: <20060222152611.13188.qmail@web32515.mail.mud.yahoo.com>
References: <20060222152611.13188.qmail@web32515.mail.mud.yahoo.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox