tgl@sss.pgh.pa.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@~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
