Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154]) by mail.postgresql.org (8.11.3/8.11.1) with ESMTP id f2SFNCU22803; Wed, 28 Mar 2001 10:23:12 -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.3/8.11.3) with ESMTP id f2SFMuw18056; Wed, 28 Mar 2001 10:22:57 -0500 (EST) To: kowalski@datrix.co.za cc: pgsql-admin@postgresql.org, pgsql-bugs@postgresql.org Subject: Re: pg_dump potential bug In-reply-to: <0103280930340B.16896@webman> References: <99pkvj$2are$1@news.tht.net> <5537.985708594@sss.pgh.pa.us> <0103280930340B.16896@webman> Comments: In-reply-to Marcin Kowalski message dated "Wed, 28 Mar 2001 09:30:34 +0200" Date: Wed, 28 Mar 2001 10:22:56 -0500 Message-ID: <18053.985792976@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200103/207 X-Sequence-Number: 1054 Marcin Kowalski writes: > Is it possible that one of the system tables has been corrupted and shows > multiple entries for the tables? Come to think of it, this is a fairly likely behavior if you have multiple entries in pg_shadow with the same usesysid. regards, tom lane