| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Michiel Lange <michiel(at)minas(dot)demon(dot)nl> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Cannot connect to the database (PG 7.3) |
| Date: | 2003-01-27 21:02:54 |
| Message-ID: | 7921.1043701374@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-hackers |
Michiel Lange <michiel(at)minas(dot)demon(dot)nl> writes:
> but, but.... it is even with the psql command...
Hmm. You didn't by any chance put a SET for session_authorization into
the per-user settings for 20020003, did you? Or the per-database
settings for whichever database he's trying to connect to? Look at
pg_shadow.useconfig and pg_database.datconfig. For that matter, I think
you could have produced this symptom by putting an entry into
postgresql.conf.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-01-27 21:52:19 | Re: VACUUM warning message. |
| Previous Message | Bruce Momjian | 2003-01-27 20:19:53 | Re: VACUUM warning message. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2003-01-27 21:09:18 | Re: IPv6 patch |
| Previous Message | Larry Rosenman | 2003-01-27 20:50:59 | Re: Request for qualified column names |