| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] PATCH: enabling parallel execution for cursors explicitly (experimental) |
| Date: | 2018-02-09 20:36:19 |
| Message-ID: | CA+TgmoaT2WKv8xEix9_vi3VOtwGoMJNKedszPPNQWg7076aqvQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Feb 9, 2018 at 7:53 AM, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
> I am not saying to allow other things. I am just replying to your
> question that why can't we use PQsetSingleRowMode. I mean to say that
> one can fetch the data parallelly via the usage of cursors (by having
> restrictions like don't allow other parallel unsafe statements) in
> plpgsql.
I'm pretty sure that other parallel-unsafe statements is an
insufficient restriction. I think we're just going around in circles
here.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | mxbi | 2018-02-09 20:48:58 | Re: configure issue - warnings sort: No such file or directory |
| Previous Message | Robert Haas | 2018-02-09 20:24:26 | Re: postgres_fdw: perform UPDATE/DELETE .. RETURNING on a join directly |