On Sat, Mar 13, 2010 at 12:10 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Bruce Momjian <bruce@momjian.us> writes:
>> Tom Lane wrote:
>>> This is making things worse, not better. You have just changed the
>>> behavior, and not in a good way. Formerly these were no-ops on
>>> a unix socket connection, and now they can throw errors.
>
>> Is this the proper way to fix the issue? Patch attached.
>
> AFAICS there is no issue, and the code is fine as-is.
>
ah! now i see this clearer... sorry for the noise
--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
Cel. +59387171157
