On Thu, Jan 29, 2009 at 12:41 PM, rhubbell <rhubb...@ihubbell.com> wrote: > On Thu, 29 Jan 2009 11:34:00 -0800 (PST) > Jeff Frost <j...@frostconsultingllc.com> wrote: > >> On Thu, 29 Jan 2009, rhubbell wrote: >> >> > Umm, because md5 doesn't work and trust does work. >> >> Generally this is because you haven't yet set a password for the postgres >> user. You have to set a password for at least the postgres user via ALTER >> ROLE while you've still got it set to trust or ident before changing to md5. > > Yeah, yeah, did all that, didn't work. Sorry, still a "Pet Peeve". (^; > While you mention it, another "Pet Peeve" was the use of ident. Yikes.
So, maybe you could tell us what "didn't work" means in a more expanded manner, along with things like error messages? md5 works a charm for me, and it has since it came out, so I'm wondering what's so different in your setup that it doesn't. -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
