| From: | "Daniel Verite" <daniel(at)manitou-mail(dot)org> |
|---|---|
| To: | "Alvaro Herrera" <alvherre(at)2ndquadrant(dot)com> |
| Cc: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>,"Tomas Vondra" <tomas(dot)vondra(at)2ndquadrant(dot)com>,"Fabien COELHO" <coelho(at)cri(dot)ensmp(dot)fr>,"vignesh C" <vignesh21(at)gmail(dot)com>,"Kyotaro Horiguchi" <horikyota(dot)ntt(at)gmail(dot)com>,peter(dot)eisentraut(at)2ndquadrant(dot)com,iwata(dot)aya(at)jp(dot)fujitsu(dot)com,"PostgreSQL Developers" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: psql - add SHOW_ALL_RESULTS option |
| Date: | 2020-01-17 18:48:00 |
| Message-ID: | 1b505687-ad27-401b-8aa4-7b37190fde20@manitou-mail.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera wrote:
> if this patch enables other psql features, it might be a good step
> forward.
Yes. For instance if the stored procedures support gets improved to
produce several result sets, how is psql going to benefit from it
while sticking to the old way (PGresult *r = PQexec(query))
of executing queries that discards N-1 out of N result sets?
Best regards,
--
Daniel Vérité
PostgreSQL-powered mailer: http://www.manitou-mail.org
Twitter: @DanielVerite
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-01-17 19:10:26 | Re: psql - add SHOW_ALL_RESULTS option |
| Previous Message | Karl O. Pinc | 2020-01-17 18:46:59 | Re: Patch to document base64 encoding |