Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f1RHMmx81443; Tue, 27 Feb 2001 12:22:48 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.1/8.11.1) with ESMTP id f1RHMa903839; Tue, 27 Feb 2001 12:22:36 -0500 (EST) To: Kyle cc: pgsql-general@postgresql.org, pgsql-sql@postgresql.org Subject: Re: [SQL] Debug messages in beta5 In-reply-to: <3A9BDA14.FFBE20A4@actarg.com> References: <3A9BDA14.FFBE20A4@actarg.com> Comments: In-reply-to Kyle message dated "Tue, 27 Feb 2001 09:47:17 -0700" Date: Tue, 27 Feb 2001 12:22:35 -0500 Message-ID: <3836.983294555@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200102/1367 X-Sequence-Number: 5328 Kyle writes: > These were interesting too: I'm not sure what to make of them: > NOTICE: Adding missing FROM-clause entry for table "cont_group_link" > ERROR: Rule WHERE condition may not contain references to other > relations > NOTICE: Adding missing FROM-clause entry for table "cont_group_link" These are fishy --- I would not have expected pg_dump output to trigger such messages. Could you redo the load with PGOPTIONS="-d2" so that the queries appear in the log along with the notices/errors? That way we could see just what's triggering the messages. regards, tom lane