Re: CLUSTER, reform_and_rewrite_tuple(), and parallelism - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: CLUSTER, reform_and_rewrite_tuple(), and parallelism
Date
Msg-id CAA4eK1LdP83O1HrpJQ0eUcX=deHkBn3EmkHKbKATXo52foO45w@mail.gmail.com
Whole thread Raw
In response to CLUSTER, reform_and_rewrite_tuple(), and parallelism  (Peter Geoghegan <pg@heroku.com>)
List pgsql-hackers
On Thu, Aug 18, 2016 at 4:42 AM, Peter Geoghegan <pg@heroku.com> wrote:
>
> Does anyone have any ideas on how to:
>
> 1). Directly address the reform_and_rewrite_tuple() bottleneck.
>
> and/or:
>
> 2). Push down some or all of the reform_and_rewrite_tuple() work till
> before tuples are passed to the tuplesort.
>
> "2" would probably make it straightforward to have
> reform_and_rewrite_tuple() work occur in parallel workers instead,
> which buys us a lot.
>

I am not aware what exactly you have in mind to parallelize Cluster
command, but anything that is CPU intensive is probably a good bet to
push down to workers (provided it is safe).

-- 
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: replication slots replicated to standbys?
Next
From: Claudio Freire
Date:
Subject: Re: [WIP] [B-Tree] Keep indexes sorted by heap physical location