From: | Konstantin Izmailov <pgfizm(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: arrays returned in text format |
Date: | 2016-03-05 16:29:00 |
Message-ID: | CAAw-Msd2RCCbWP+Kz0jnWxjjMsiT_0gCcPTk=NVCA1PiTDHOFQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Tom, I was unable to reproduce the issue with standard libpq. Moreover, I
found why it was returned as Text. It was actually a bug in passing
resultFormats in the Bind message. Sorry for the false alert, my fault.
Thank you for the help!
Konstantin
On Fri, Mar 4, 2016 at 10:52 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Konstantin Izmailov <pgfizm(at)gmail(dot)com> writes:
> > Whole point of my question was why PG does not return
> > binary formatted field when requested (this is a feature supported in the
> > protocol).
>
> You haven't presented a test case demonstrating that that happens in
> unmodified community source code. If it does happen, I'd be happy to look
> into it, because I agree it'd be a bug. But I have other things to spend
> my time on than reverse-engineering test cases out of code fragments
> dependent on incompletely-described custom modifications of Postgres.
>
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | Francisco Olarte | 2016-03-05 18:53:04 | Re: multiple UNIQUE indices for FK |
Previous Message | Emre Hasegeli | 2016-03-05 14:23:09 | Re: Custom column ordering |