Your pg_hba.conf file will be configured to allow TRUST (ie, no password)
authentication for the computers you are connecting from, most likely your
local network subnet such as 192.168.0.1/24
Have a look in there and see, if you need help, copy and paste the
pg_hba.conf settings (excluding comments) to the group for us.
Cheers,
~p
-----Original Message-----
From: pgsql-admin-owner@postgresql.org
[mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Sabin Coanda
Sent: Thursday, 22 March 2007 23:36
To: pgsql-admin@postgresql.org
Subject: [ADMIN] set password doesn't work
Hi,
I installed on linux the dbms "PostgreSQL 8.2.3 on i686-redhat-linux-gnu,
compiled by GCC gcc (GCC) 4.0.2 20051125 (Red Hat 4.0.2-8)".
Initially I set an empty password for the user postgres.
Some times later I connect from a different machine (Windows) to that
database, and I set a password for postgres user, and now I see it in
pgAdmin as:
CREATE ROLE postgres LOGIN
ENCRYPTED PASSWORD 'md505a74e1678967a543fd92e711aa5762d'
SUPERUSER INHERIT CREATEDB CREATEROLE;
Surprising I was able to connect now to that database server, without
password, or specifying any text as password, both from the different
machine, and from the same database server machine.
So then I tried to change the password by the following script:
ALTER USER postgres WITH ENCRYPTED PASSWORD '...';
But nothing change, and it has the same behaviour like an empty password.
What's wrong ? Please let me know if I applied the right procedure to set
the password for postgres user.
TIA,
Sabin
---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings
*******************Confidentiality and Privilege Notice*******************
The material contained in this message is privileged and confidential to
the addressee. If you are not the addressee indicated in this message or
responsible for delivery of the message to such person, you may not copy
or deliver this message to anyone, and you should destroy it and kindly
notify the sender by reply email.
Information in this message that does not relate to the official business
of Weatherbeeta must be treated as neither given nor endorsed by Weatherbeeta.
Weatherbeeta, its employees, contractors or associates shall not be liable
for direct, indirect or consequential loss arising from transmission of this
message or any attachments
