Re: statement logging / extended query protocol issues - Mailing list pgsql-hackers

From Tom Lane
Subject Re: statement logging / extended query protocol issues
Date
Msg-id 3922.1125949107@sss.pgh.pa.us
Whole thread Raw
In response to Re: statement logging / extended query protocol issues  (Simon Riggs <simon@2ndquadrant.com>)
Responses Re: statement logging / extended query protocol issues
List pgsql-hackers
Simon Riggs <simon@2ndquadrant.com> writes:
> +     /*
> +      * If we re-issue an Execute protocol request against an existing
> +      * portal, then we are only fetching more rows rather than 
> +      * completely re-executing the query from the start
> +      */
> +     if (!portal->atEnd)
> +         subsequent_fetch = true;

That strikes me as a completely bogus test for a "re-issued" execute.
Did you mean !atStart?

Also, why is it a good idea to report the number of rows fetched in
some cases (and not others)?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: PostgreSQL configurable SSL key checking
Next
From: Tom Lane
Date:
Subject: Re: PostgreSQL configurable SSL key checking