Re: Inefficiency in parallel pg_restore with many tables

Nathan Bossart <nathandbossart@gmail.com>

From: Nathan Bossart <nathandbossart@gmail.com>

To: Robert Haas <robertmhaas@gmail.com>

Cc: Tom Lane <tgl@sss.pgh.pa.us>, Alvaro Herrera <alvherre@alvh.no-ip.org>, Andrew Dunstan <andrew@dunslane.net>, pgsql-hackers@lists.postgresql.org

Date: 2023-09-04T23:08:29Z

Lists: pgsql-hackers

Attachments

v7-0001-Allow-binaryheap-to-use-any-type.patch (text/x-diff)

On Sat, Sep 02, 2023 at 11:55:21AM -0700, Nathan Bossart wrote:
> I ended up hacking together a (nowhere near committable) patch to see how
> hard it would be to allow using any type with binaryheap.  It doesn't seem
> too bad.

I spent some more time on this patch and made the relevant adjustments to
the rest of the set.

-- 
Nathan Bossart
Amazon Web Services: https://aws.amazon.com

Commits

Remove open-coded binary heap in pg_dump_sort.c.
- 559bc1732180 17.0 landed
Convert pg_restore's ready_list to a priority queue.
- 9bfd44bbde42 17.0 landed
Add function for removing arbitrary nodes in binaryheap.
- c103d073819a 17.0 landed
Make binaryheap available to frontend code.
- 5af0263afd7b 17.0 landed