It is, somehow, not possible to connect as a user which name is completely numeric. I did a few tests on the same machine, and this is the outcome:
psql -h myhost -d mydb -U postgres -> connects fine
CREATE USER "12345" WITH PASSWORD 'secret';
CREATE USER
\q
psql -h myhost -d mydb -U 12345 -> error
psql -h myhost -d mydb -U "12345" -> error
psql -h myhost -d mydb -U '12345' -> error
psql -h myhost -d mydb -U postgres
DROP USER "12345";
DROP USER
CREATE USER n12345 WITH PASSWORD 'secret';
CREATE USER
\q
psql -h myhost -d mydb -U n12345 -> connects fine!
I think this is a bug, I will report it as one anyways... who knows what comes from it...
it is not nice that the DBMS does not prevent me from creating a user that cannot connect...
so either it should be prevented or possible...
But thanks for thinking along with me...
Michiel
At 14:19 27-1-2003 +0100, Michiel Lange wrote:
it is at connect-time, so there is nothing done with set session authorization.
I just want to connect, and read data from a table to which the group the user is in has read-access.
I have tried if it would differ when I try to connect with a user created like:
CREATE USER 20020003 WITH ENCRYPTED PASSWORD 'secret';
or
CREATE USER 20020004 WITH UNENCRYPTED PASSWORD 'secred';
it would not matter... even if there really is a trust-relation between my computer and the other machine in pg_hba.conf
it is pretty strange... might it be a bug?
Thanks for the try though,
Michiel
At 19:42 26-1-2003 -0500, Tom Lane wrote:
Michiel Lange <[EMAIL PROTECTED]> writes: > I get this error message: > psql: FATAL: permission deniedAs near as I can tell, you must have some code that is trying to do SET SESSION AUTHORIZATION --- which only a superuser is allowed to do. Evidently user 20020003 isn't one. regards, tom lane
---------------------------(end of broadcast)--------------------------- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html