Re: improve PQexec documentation - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: improve PQexec documentation
Date
Msg-id CA+hUKGKYAxfFy1-zj72HRYkRAcB5=WjpfmVAR2+0SswaPfqrwQ@mail.gmail.com
Whole thread Raw
In response to Re: improve PQexec documentation  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers
On Sat, Apr 13, 2019 at 1:12 AM Alvaro Herrera <alvherre@2ndquadrant.com> wrote:
> I'm inclined to reject this patch.

On Fri, Jul 5, 2019 at 6:47 PM Peter Eisentraut
<peter.eisentraut@2ndquadrant.com> wrote:
> But you're not really supposed to use it for multiple queries or
> multiple result sets anyway.  There are other functions for this.
>
> If a source code comment in libpq or psql would help explaining some of
> the current code, then we could add that.  But I am also not sure that
> enshrining the current behavior on the API documentation is desirable.

Hi Fabien,

Based on the above, I have marked this as "Returned with feedback".

-- 
Thomas Munro
https://enterprisedb.com



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: concerns around pg_lsn
Next
From: Michael Paquier
Date:
Subject: Re: allow online change primary_conninfo