Re: Improving scalability of Parallel Bitmap Heap/Index Scan - Mailing list pgsql-hackers

From David Geier
Subject Re: Improving scalability of Parallel Bitmap Heap/Index Scan
Date
Msg-id 5498c845-8872-4092-8e8c-7ce6e3b75f5a@googlemail.com
Whole thread
In response to Re: Improving scalability of Parallel Bitmap Heap/Index Scan  (John Naylor <john.naylor@enterprisedb.com>)
Responses Re: Improving scalability of Parallel Bitmap Heap/Index Scan
List pgsql-hackers
Hi John,

> On this note, there has been a proposed (but as far as I know untested)
> patch to speed up this sort in a much simpler way, in this thread
> 
> https://www.postgresql.org/message-id/
> CA%2BhUKGKztHEWm676csTFjYzortziWmOcf8HDss2Zr0muZ2xfEg%40mail.gmail.com
> <https://www.postgresql.org/message-id/
> CA%2BhUKGKztHEWm676csTFjYzortziWmOcf8HDss2Zr0muZ2xfEg%40mail.gmail.com>
> 
> where you may find this patch
> 
> https://www.postgresql.org/message-id/attachment/120560/0007-Specialize-
> pagetable-sort-routines-in-tidbitmap.c.patch <https://
> www.postgresql.org/message-id/attachment/120560/0007-Specialize-
> pagetable-sort-routines-in-tidbitmap.c.patch>

Thanks for the pointer. I've applied that change to my patch set. See
other mail. It helped a lot further reducing the sort time in each
parallel worker.

--
David Geier



pgsql-hackers by date:

Previous
From: David Geier
Date:
Subject: Re: Improving scalability of Parallel Bitmap Heap/Index Scan
Next
From: Nisha Moond
Date:
Subject: Re: Fix apply worker crash when subscriber table has only a deferrable primary key