On Fri, Jan 30, 2009 at 7:55 AM, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> wrote:
> On Thu, Jan 29, 2009 at 12:41 PM, rhubbell <Rhubbell(at)ihubbell(dot)com> wrote:
>> On Thu, 29 Jan 2009 11:34:00 -0800 (PST)
>> Jeff Frost <jeff(at)frostconsultingllc(dot)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.
We've had hundreds of thousands (more likely millions by now) of
downloads of the community and EDB installers which all use md5 out of
the box, and I don't recall ever seeing anyone complain it doesn't
EnterpriseDB UK: http://www.enterprisedb.com
In response to
pgsql-general by date
|Next:||From: Scara Maccai||Date: 2009-01-30 08:35:53|
|Subject: complex custom aggregate function|
|Previous:||From: Scott Marlowe||Date: 2009-01-30 07:55:38|
|Subject: Re: md5 doesn't work (Was Re: Pet Peeves?)|