pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedWARNING: foreign key constraint will require costly sequential scans during pg_restore
2+ messages / 2 participants
[nested] [flat]
* WARNING: foreign key constraint will require costly sequential scans during pg_restore
@ 2006-02-22 15:26 CG <cgg007@yahoo.com>
2006-02-22 15:30 ` Re: WARNING: foreign key constraint will require costly sequential scans during pg_restore Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 1 reply; 2+ messages in thread
From: CG @ 2006-02-22 15:26 UTC (permalink / raw)
To: pgsql-admin
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
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: WARNING: foreign key constraint will require costly sequential scans during pg_restore
2006-02-22 15:26 WARNING: foreign key constraint will require costly sequential scans during pg_restore CG <cgg007@yahoo.com>
@ 2006-02-22 15:30 ` Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 0 replies; 2+ messages in thread
From: Tom Lane @ 2006-02-22 15:30 UTC (permalink / raw)
To: cgg007@yahoo.com; +Cc: pgsql-admin
CG <cgg007@yahoo.com> writes:
> 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.
That seems a bit odd. Would you provide a test case?
regards, tom lane
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2006-02-22 15:30 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2006-02-22 15:26 WARNING: foreign key constraint will require costly sequential scans during pg_restore CG <cgg007@yahoo.com>
2006-02-22 15:30 ` Tom Lane <tgl@sss.pgh.pa.us>
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