it will differ if I put a -U parameter with postgres or 20020003
postgres, michiel or most other names will connect fine, however the user 20020003 will not...
I get that FATAL error... all users should be able to connect to the database, according to pg_hba.conf
and when I do: SELECT * FROM pg_user; I get all users, including 20020003 returned... and 20030003 has userid 106, which is mentioned in the list SELECT * FROM pg_group; so, the account should be set up correctly. A ALTER USER 20020003 WITH ... has not helped either, but I am very certain the user exists... but is not allowed to connect to the database...
But I will try to see what happens with query logging... never thought that connecting would issue a query as well... not so strange an idea though... I'll check it out...
Michiel
At 09:10 27-1-2003 -0500, Tom Lane wrote:
Michiel Lange <[EMAIL PROTECTED]> writes: > it is pretty strange... might it be a bug?I'm quite sure it's a bug in your code. Try turning on query logging so you can see what queries are being issued; maybe that will help solve the problem. regards, tom lane
---------------------------(end of broadcast)--------------------------- TIP 6: Have you searched our list archives? http://archives.postgresql.org