Re: using custom scan nodes to prototype parallel sequential scan

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: using custom scan nodes to prototype parallel sequential scan
Date: 2014-11-14 00:27:07
Message-ID: CA+U5nMJMFJ=ZXs_JnEVhfh9k6Qig2tMmhQFPakx3B8K6WEaRtg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 12 November 2014 00:54, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Tue, Nov 11, 2014 at 3:29 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
>> * only functions marked as "CONTAINS NO SQL"
>> We don't really know what proisparallel is, but we do know what
>> CONTAINS NO SQL means and can easily check for it.
>> Plus I already have a patch for this, slightly bitrotted.
>
> Interestingly, I have a fairly solid idea of what proisparallel is,
> but I have no clear idea what CONTAINS NO SQL is or why it's relevant.
> I would imagine that srandom() contains no SQL under any reasonable
> definition of what that means, but it ain't parallel-safe.

What is wrong in generating random numbers in parallel?

But I'm sure many volatile functions would be annoying to support, so
CONTAINS NO SQL and STABLE/IMMUTABLE seems OK for the first thing.

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2014-11-14 00:30:29 Re: Teaching pg_dump to use NOT VALID constraints
Previous Message Simon Riggs 2014-11-14 00:19:04 Re: using custom scan nodes to prototype parallel sequential scan