Received: from localhost (pluto.hub.org [200.46.204.4]) by postgresql.org (Postfix) with ESMTP id 7E1CF9F9ED7 for ; Thu, 16 Nov 2006 02:32:37 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.4]) (amavisd-new, port 10024) with ESMTP id 36442-02 for ; Thu, 16 Nov 2006 02:32:29 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 47ECC9F9ECD for ; Thu, 16 Nov 2006 02:32:35 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id kAG6WZtG012937; Thu, 16 Nov 2006 01:32:35 -0500 (EST) To: Will Cameron cc: pgsql-admin@postgresql.org Subject: Re: all postgres users do "not exist" In-reply-to: <20061115193107.64930.qmail@web62404.mail.re1.yahoo.com> References: <20061115193107.64930.qmail@web62404.mail.re1.yahoo.com> Comments: In-reply-to Will Cameron message dated "Wed, 15 Nov 2006 11:31:07 -0800" Date: Thu, 16 Nov 2006 01:32:35 -0500 Message-ID: <12936.1163658755@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200611/158 X-Sequence-Number: 23685 Will Cameron writes: > We are using (PostgreSQL) 8.0.1 for Solaris. Apparently our > postgres users were wiped out somehow, for I cannot even log in as > superuser "postgres". Our pg_hba.conf settings are as loose as possible > ("trust"). This problem started mid session after we ran a .sql script > to upgrade a DSpace digital library database within the postgres system. Better take a closer look at what that script did. Meanwhile, you can probably get out of this by starting a standalone postgres session and using it to recreate your SQL users. regards, tom lane