| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
| Cc: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PATCH: enabling parallel execution for cursors explicitly (experimental) |
| Date: | 2017-11-02 01:55:27 |
| Message-ID: | CA+TgmoYWoqDUViwPTk-rOJbGG8aqEVAQWBgauVbYaUxznSA==g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Nov 1, 2017 at 7:49 AM, Craig Ringer <craig(at)2ndquadrant(dot)com> wrote:
> If the client wants to fetch in chunks it can use a portal and limited
> size fetches. That shouldn't (?) be parallel-unsafe, since nothing
> else can happen in the middle anyway.
I believe sending a limited-size fetch forces serial execution
currently. If it's true that nothing else can happen in the middle
then we could relax that, but I don't see why that should be true?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2017-11-02 02:01:48 | Re: PATCH: enabling parallel execution for cursors explicitly (experimental) |
| Previous Message | Peter Eisentraut | 2017-11-02 01:33:52 | Re: Statement-level rollback |