X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id C159F9DC87E for ; Wed, 22 Feb 2006 11:26:12 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 31355-04 for ; Wed, 22 Feb 2006 11:26:17 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from web32515.mail.mud.yahoo.com (web32515.mail.mud.yahoo.com [68.142.207.225]) by postgresql.org (Postfix) with SMTP id 3DFDE9DC857 for ; Wed, 22 Feb 2006 11:26:10 -0400 (AST) Received: (qmail 13190 invoked by uid 60001); 22 Feb 2006 15:26:11 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=oP71EyGV6zGucvWitNBF0muifotwWHR+59z8H0KxDmHYNguNLFEyG3zjmeQlPQsCYvT1018jgadzolI+h3SjJ361Ko7KviyEdkixGuu0MRdqKtid8nd6hDV+vTeWufaqTiyySCYsY4PDU40StTc1O1aSh73RmpOWqY5Qi7vTUOc= ; Message-ID: <20060222152611.13188.qmail@web32515.mail.mud.yahoo.com> Received: from [216.173.173.66] by web32515.mail.mud.yahoo.com via HTTP; Wed, 22 Feb 2006 07:26:11 PST Date: Wed, 22 Feb 2006 07:26:11 -0800 (PST) From: CG Reply-To: cgg007@yahoo.com Subject: WARNING: foreign key constraint will require costly sequential scans during pg_restore To: pgsql-admin@postgresql.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=1.196 required=5 tests=[AWL=-0.162, DNS_FROM_RFC_ABUSE=0.479, DNS_FROM_RFC_WHOIS=0.879] X-Spam-Score: 1.196 X-Spam-Level: * X-Archive-Number: 200602/260 X-Sequence-Number: 20681 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