From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
---|---|
To: | Peter Geoghegan <pg(at)heroku(dot)com> |
Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: CLUSTER, reform_and_rewrite_tuple(), and parallelism |
Date: | 2016-08-20 04:50:28 |
Message-ID: | CAA4eK1LdP83O1HrpJQ0eUcX=deHkBn3EmkHKbKATXo52foO45w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Aug 18, 2016 at 4:42 AM, Peter Geoghegan <pg(at)heroku(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Claudio Freire | 2016-08-20 04:53:30 | Re: [WIP] [B-Tree] Keep indexes sorted by heap physical location |
Previous Message | Michael Paquier | 2016-08-20 04:43:42 | Re: replication slots replicated to standbys? |