Re: [HACKERS] PATCH: enabling parallel execution for cursorsexplicitly (experimental) - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: [HACKERS] PATCH: enabling parallel execution for cursorsexplicitly (experimental)
Date
Msg-id CANP8+jJBHDu+kgH2Jy34zzx9C5x61LF7JkWODPaRKuXMhD0vKw@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] PATCH: enabling parallel execution for cursorsexplicitly (experimental)  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On 2 November 2017 at 01:55, Robert Haas <robertmhaas@gmail.com> wrote:
> On Wed, Nov 1, 2017 at 7:49 AM, Craig Ringer <craig@2ndquadrant.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?

Perhaps the question is not "why" but "when"?

If a parallel cursor is requested, we could simply prevent other
intermediate commands other than FETCH (next).

-- 
Simon Riggs                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: [HACKERS] PATCH: enabling parallel execution for cursorsexplicitly (experimental)
Next
From: Peter Eisentraut
Date:
Subject: Re: Package version in PG_VERSION and version()