| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Colin 't Hart" <cthart(at)yahoo(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: [HACKERS] psql and security |
| Date: | 2001-09-21 14:32:33 |
| Message-ID: | 28085.1001082753@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
"Colin 't Hart" <cthart(at)yahoo(dot)com> writes:
> Does postgres have a concept of a 'root' user? Then the password should
> only be prompted when one isn't root; ie. adopt Unix semantics.
Can't really do that in psql's \c, since it's establishing a whole new
connection; there is no possibility for superuserness on the old
connection to provide any relaxation of the check.
However, see SET SESSION AUTHORIZATION, which does what you're thinking
of within the context of a single connection.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Boris Pran | 2001-09-21 14:33:38 | functions compiled with g++ |
| Previous Message | Tom Lane | 2001-09-21 14:29:38 | Re: psql and security |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-09-21 14:36:38 | Re: psql and security |
| Previous Message | Tom Lane | 2001-09-21 14:29:38 | Re: psql and security |