From: | "Magnus Hagander" <mha(at)sollentuna(dot)net> |
---|---|
To: | "Tom Lane" <tgl(at)postgresql(dot)org>, <pgsql-committers(at)postgresql(dot)org> |
Subject: | Re: pgsql: Ooops, ldap fix for win32 broke the non-win32 case. |
Date: | 2006-08-22 07:42:16 |
Message-ID: | 6BCB9D8A16AC4241919521715F4D8BCEA3556F@algol.sollentuna.se |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Argh. And I was so certain I only touched the win32 code path. I
should've tested it on my linux box as well... Sorry about that!
//Magnus
> -----Original Message-----
> From: pgsql-committers-owner(at)postgresql(dot)org [mailto:pgsql-
> committers-owner(at)postgresql(dot)org] On Behalf Of Tom Lane
> Sent: Tuesday, August 22, 2006 4:24 AM
> To: pgsql-committers(at)postgresql(dot)org
> Subject: pgsql: Ooops, ldap fix for win32 broke the non-win32 case.
>
> Log Message:
> -----------
> Ooops, ldap fix for win32 broke the non-win32 case.
>
> Modified Files:
> --------------
> pgsql/src/backend/libpq:
> auth.c (r1.140 -> r1.141)
>
> (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/libpq
> /auth.c.diff?r1=1.140&r2=1.141)
>
> ---------------------------(end of broadcast)----------------------
> -----
> TIP 3: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faq
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2006-08-22 12:11:28 | pgsql: In new "invalid byte sequence" error hint, call it "error", not |
Previous Message | Bruce Momjian | 2006-08-22 03:40:39 | pgsql: Add info for get_* functions: > > These would be for |