Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id 7097C9F94EA for ; Wed, 15 Nov 2006 15:38:09 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 93236-03 for ; Wed, 15 Nov 2006 19:37:49 +0000 (UTC) X-Greylist: delayed 00:06:40.441509 by SQLgrey- Received: from web62404.mail.re1.yahoo.com (web62404.mail.re1.yahoo.com [69.147.75.81]) by postgresql.org (Postfix) with SMTP id 402B69F946B for ; Wed, 15 Nov 2006 15:37:49 -0400 (AST) Received: (qmail 64932 invoked by uid 60001); 15 Nov 2006 19:31:07 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=ne4gjhtjUQrVPrO4Rfzcou0YQ0gg7kPERB3up/uZ4tffXUGfDxSSlSclfu3eDE9fTF3OmwzGWxBqPzoD3pMm+KxjrbTD8mqTR4P6Tiy/J0iAHyKYKiNtbkpdspFoXUSqps5W4lGrUVhUaPX5MypgoYJYI6fVdAYZE1qNfkBXcks= ; Message-ID: <20061115193107.64930.qmail@web62404.mail.re1.yahoo.com> Received: from [153.104.201.26] by web62404.mail.re1.yahoo.com via HTTP; Wed, 15 Nov 2006 11:31:07 PST Date: Wed, 15 Nov 2006 11:31:07 -0800 (PST) From: Will Cameron Subject: all postgres users do "not exist" To: pgsql-admin@postgresql.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-1892475969-1163619067=:64508" Content-Transfer-Encoding: 8bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=2.38 tagged_above=0 required=5 tests=BAYES_05, DNS_FROM_RFC_ABUSE, DNS_FROM_RFC_POST, DNS_FROM_RFC_WHOIS, HTML_50_60, HTML_MESSAGE X-Spam-Level: ** X-Archive-Number: 200611/156 X-Sequence-Number: 23683 --0-1892475969-1163619067=:64508 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Hello, 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. This action should not have affected postgres users in any way. We did not modify the template1 database (which affects users?) or anything of that sort. The only other oddity of our installation I can think of is that fact that the local data directory (/usr/local/pgsql/data) points to another data directory at the root of the postgres unix account which really contains the database data (/home/local/pgsql/data). Is there any way to reinitialize while preserving the existing data directory (dbinit??)? Thanks, Will Cameron clusterdb droplang pg_config pg_resetxlog vacuumdb createdb dropuser pg_controldata pg_restore createlang ecpg pg_ctl postgres createuser initdb pg_dump postmaster dropdb ipcclean pg_dumpall psql bash-2.05$ psql -l psql: FATAL: user "postgres" does not exist bash-2.05$ who am i postgres pts/5 Nov 15 00:18 (g83-sb1-1.csc.villanova.edu) bash-2.05$ su postgres Password: bash-2.05$ export LD_LIBRARY_PATH bash-2.05$ LD_LIBRARY_PATH=/usr/local/lib bash-2.05$ psql -l psql: FATAL: user "postgres" does not exist pg_hba.conf: # TYPE DATABASE USER CIDR-ADDRESS METHOD # "local" is for Unix domain socket connections only local all all trust # IPv4 local connections: host all all 127.0.0.1/32 trust # IPv6 local connections: host all all ::1/128 trust host dspace dspace 127.0.0.1 255.255.255.255 md5 --------------------------------- Sponsored Link Mortgage rates as low as 4.625% - $150,000 loan for $579 a month. Intro-*Terms --0-1892475969-1163619067=:64508 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: 8bit  Hello,

    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.
 This action should not have affected postgres users in any way.  We did
not modify the template1 database (which affects users?) or anything of
that sort.  The only other oddity of our installation I can think of is
that fact that the local data directory (/usr/local/pgsql/data) points
to another data directory at the root of the postgres unix account which
really contains the database data (/home/local/pgsql/data).  Is there
any way to reinitialize while preserving the existing data directory
(dbinit??)?   
  
  Thanks,
Will Cameron

clusterdb       droplang        pg_config       pg_resetxlog    vacuumdb
createdb        dropuser        pg_controldata  pg_restore
createlang      ecpg            pg_ctl          postgres
createuser      initdb          pg_dump         postmaster
dropdb          ipcclean        pg_dumpall      psql
bash-2.05$ psql -l
psql: FATAL:  user "postgres" does not exist
bash-2.05$ who am i
postgres   pts/5        Nov 15 00:18    (g83-sb1-1.csc.villanova.edu)
bash-2.05$ su postgres
Password:
bash-2.05$ export LD_LIBRARY_PATH
bash-2.05$ LD_LIBRARY_PATH=/usr/local/lib
bash-2.05$ psql -l
psql: FATAL:  user "postgres" does not exist



pg_hba.conf:


# TYPE  DATABASE    USER        CIDR-ADDRESS          METHOD

# "local" is for Unix domain socket connections only
local   all         all                               trust
# IPv4 local connections:
host    all         all         127.0.0.1/32          trust
# IPv6 local connections:
host    all         all         ::1/128               trust
host dspace dspace 127.0.0.1 255.255.255.255 md5


Sponsored Link

Mortgage rates as low as 4.625% - $150,000 loan for $579 a month. Intro-*Terms --0-1892475969-1163619067=:64508--