| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Dave Cramer <davecramer(at)gmail(dot)com> |
| Cc: | Tatsuo Ishii <ishii(at)postgresql(dot)org>, david(dot)g(dot)johnston(at)gmail(dot)com, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Protocol question regarding Portal vs Cursor |
| Date: | 2024-07-27 19:18:43 |
| Message-ID: | 2009631.1722107923@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Dave Cramer <davecramer(at)gmail(dot)com> writes:
> On Sat, 27 Jul 2024 at 01:55, Tatsuo Ishii <ishii(at)postgresql(dot)org> wrote:
>>> So while the API's are "virtually" identical AFAICT there is no way to
>>> create a "WITH HOLD" portal ?
> Yes, sorry, I should have said one can not create a with hold portal using
> the BIND command
Yeah. The two APIs (cursors and extended query protocol) manipulate
the same underlying Portal objects, but the features exposed by the
APIs aren't all identical. We've felt that this isn't high priority
to sync up, since you can create a Portal with one API then manipulate
it through the other if need be.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2024-07-27 19:40:09 | Re: add function argument names to regex* functions. |
| Previous Message | Joseph Koshakow | 2024-07-27 19:18:00 | Fix overflow in pg_size_pretty |