| From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: improve PQexec documentation |
| Date: | 2019-08-01 09:12:35 |
| Message-ID: | CA+hUKGKYAxfFy1-zj72HRYkRAcB5=WjpfmVAR2+0SswaPfqrwQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Apr 13, 2019 at 1:12 AM Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> wrote:
> I'm inclined to reject this patch.
On Fri, Jul 5, 2019 at 6:47 PM Peter Eisentraut
<peter(dot)eisentraut(at)2ndquadrant(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2019-08-01 09:13:58 | Re: allow online change primary_conninfo |
| Previous Message | Michael Paquier | 2019-08-01 09:12:29 | Re: concerns around pg_lsn |