Re: Segmentation fault: pg_upgrade 9.1 to 9.3: pg_dump: row number 0 is out of range 0..-1 - Mailing list pgsql-general

From Tom Lane
Subject Re: Segmentation fault: pg_upgrade 9.1 to 9.3: pg_dump: row number 0 is out of range 0..-1
Date
Msg-id 11373.1382795586@sss.pgh.pa.us
Whole thread Raw
In response to Re: Segmentation fault: pg_upgrade 9.1 to 9.3: pg_dump: row number 0 is out of range 0..-1  (Alan Nilsson <anilsson@apple.com>)
Responses Re: Segmentation fault: pg_upgrade 9.1 to 9.3: pg_dump: row number 0 is out of range 0..-1  (Alan Nilsson <anilsson@apple.com>)
List pgsql-general
Alan Nilsson <anilsson@apple.com> 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


pgsql-general by date:

Previous
From: Marc Mamin
Date:
Subject: Re: Detecting change in event properties
Next
From: Tomas Vondra
Date:
Subject: Re: Increasing CPU usage of PostgreSQL