From: | Chris Browne <cbbrowne(at)acm(dot)org> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: control pg_hba.conf via SQL |
Date: | 2006-03-30 17:46:12 |
Message-ID: | 60zmj7q10b.fsf@dba2.int.libertyrms.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
tgl(at)sss(dot)pgh(dot)pa(dot)us (Tom Lane) writes:
> If your pg_hba.conf looks like
> host all all 0.0.0.0/32 md5
> there's not much call to update it dynamically ...
There's one case, where .pgpass got hosed, and you didn't have a
backup of it, and need to assign new passwords...
I once ran into a case like this, where nobody had bothered to record
the "postgres" user's password, and had to override md5 authentication
in order to get in and reset passwords...
--
(format nil "~S(at)~S" "cbbrowne" "acm.org")
http://www3.sympatico.ca/cbbrowne/lisp.html
"When I was a boy of fourteen, my father was so ignorant I could
hardly stand to have the old man around. But when I got to be
twenty-one, I was astonished at how much the old man had learned in
seven years." -- Mark Twain
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2006-03-30 18:27:25 | Re: control pg_hba.conf via SQL |
Previous Message | Chris Browne | 2006-03-30 17:43:33 | Re: control pg_hba.conf via SQL |