Re: _mdfd_getseg can be expensive - Mailing list pgsql-hackers

From Andres Freund
Subject Re: _mdfd_getseg can be expensive
Date
Msg-id 20160819004232.rzfjbnubizthtgl7@alap3.anarazel.de
Whole thread Raw
In response to Re: _mdfd_getseg can be expensive  (Peter Geoghegan <pg@heroku.com>)
Responses Re: _mdfd_getseg can be expensive  (Peter Geoghegan <pg@heroku.com>)
List pgsql-hackers
On 2016-08-18 17:35:47 -0700, Peter Geoghegan wrote:
> On Thu, Aug 18, 2016 at 5:28 PM, Andres Freund <andres@anarazel.de> wrote:
> >> I can review this next week.
> >
> > Thanks
> 
> Given the time frame that you have in mind, I won't revisit the
> question the parallel CLUSTER CPU bottleneck issue until this is
> committed. The patch might change things enough that that would be a
> waste of time.

How large was the index & table in question? I mean this really only
comes into effect at 100+ segments.



pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: _mdfd_getseg can be expensive
Next
From: Peter Geoghegan
Date:
Subject: Re: _mdfd_getseg can be expensive