From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Arcady Genkin <a(dot)genkin(at)utoronto(dot)ca> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Authenticating user `postgres' |
Date: | 2001-09-26 19:57:35 |
Message-ID: | 9580.1001534255@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Arcady Genkin <a(dot)genkin(at)utoronto(dot)ca> writes:
> The problem I'm having is that I want local UNIX user `postgres', who
> is the database superuser, to be able to connect to any database
> without a password.
You can't make postgres' life any easier than you make it for anyone
else coming from the same machine, because the authentication mechanism
is chosen on the basis of the client machine and (possibly) the target
database --- not on the basis of who the user is. Offhand I'd think it
foolish to make it easier to get into the superuser account than regular
accounts anyway.
One possibility is to run an IDENT daemon and allow ident-authenticated
connections from 127.0.0.1. Then "pg_dumpall -h localhost" would work
without a password. Trusting other people's IDENT daemons is widely
considered a bad idea, but I see no reason not to trust your own.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Randal L. Schwartz | 2001-09-26 20:14:02 | Re: Birthsday list |
Previous Message | Mitch Vincent | 2001-09-26 19:10:36 | Re: PgAdmin for 7.1.3 |