| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: cursors with prepared statements |
| Date: | 2018-06-12 13:49:09 |
| Message-ID: | CAA4eK1Lr4fdo6JqHJ=VFHCMDEQTZenXUN8N4ax6GPWHR=TauBw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jun 11, 2018 at 9:56 PM, Peter Eisentraut
<peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:
> On 6/11/18 09:57, Amit Kapila wrote:
>> Sounds like a reasonable approach. Have you not considered using a
>> special OPEN syntax because there are some other forms of problems
>> with it?
>
> There is no OPEN command in direct SQL. Do you mean whether I have
> considered introducing an OPEN command?
>
Yes.
> Yes, but it seems to me that
> that would create weird inconsistencies and doesn't seem very useful in
> practice.
>
Okay, if that doesn't make the job easy, then there is not much use in
pursuing that direction.
--
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-06-12 13:50:56 | Re: late binding of shared libs for C functions |
| Previous Message | Peter Eisentraut | 2018-06-12 13:37:24 | Re: assert in nested SQL procedure call in current HEAD |