oops sorry to be unclear, the code below is my code in my app.
What I am saying is that something changed in 90300 that causes libpq to spew to stdout where it had not in libpq 90102 & 90203.
I guess i am blaming the messenger because there should be no messenger. Regardless of how badly I mangle the use of libpq, it should not be sending anything to stdout.
alan
On Oct 26, 2013, at 6:53 AM, Tom Lane <tgl@xxxxxxxxxxxxx> wrote:
> Alan Nilsson <anilsson@xxxxxxxxx> writes:
>> I ran into something tonight that seems relevant here, or certainly related:
>> I recently updated my app(s) libpq version from 9.1 to 9.3 and immediately I starting seeing:
>
>> row number 0 is out of range 0..-1
>
>> spewed to stdout.
>
>> I traced it down to this code:
>
>> if (PQresultStatus(result) == PGRES_TUPLES_OK){
>> if (!PQgetisnull(result, 0, 0)){
>> ......
>> }
>> }
>
> I can find no code like that in the PG sources --- everyplace that does
> "PQgetisnull(result, 0, 0)" prefaces it with a check that there's at least
> one row in the result. I think you're blaming the messenger.
>
> regards, tom lane
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
