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 f1S49Gx53268 for ; Tue, 27 Feb 2001 23:09:16 -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 f1S492916772; Tue, 27 Feb 2001 23:09:02 -0500 (EST) To: Tubagus Nizomi cc: pgsql-sql@postgresql.org Subject: Re: Error ?? In-reply-to: <01022808555801.01280@nizomi> References: <01022808555801.01280@nizomi> Comments: In-reply-to Tubagus Nizomi message dated "Wed, 28 Feb 2001 08:55:58 +0700" Date: Tue, 27 Feb 2001 23:09:02 -0500 Message-ID: <16769.983333342@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200102/419 X-Sequence-Number: 1624 Tubagus Nizomi writes: > NOTICE: get_groname: group 0 not found > getTables(): SELECT failed. Explanation from backend: 'pqReadData() -- > backend closed the channel unexpectedly. I think you dropped a user that was still a member of a group, or a group still referred to in a table's permissions, or something like that. Look into pg_user and pg_group, and look at the permissions of the table you were trying to access. We have fixed a couple of bugs like this in current sources, but I'd like to know the details when you have them, just to make sure this case is covered now ... regards, tom lane