Skip to main content


Short Description

Waiting to elect a Parallel Hash participant to allocate more batches.

Additional Information

In parallel hash queries, a number of hash tables are used and both sides of the join are split into batches. PostgreSQL tries to calculate the number of batches before loading. This wait is seen while electing a parallel hash participant to grow the number of batches.

How to reduce this wait

Parallel queries are excellent at scanning large amounts of data the quickly returning results. Run in isolation or in a considered manner they are a useful tool.

Do not allow concurrent parallel queries from many users to flood system CPU or IO resources.

Adjust max_worker_process , max_parallel_workers and max_parallel_workers_per_gather to control response of your query and overall impact to the system.

PostgreSQL documentation - Parallel Query

PostgreSQL documentation - The Statistics Collector

EDB - Parallel Hash Joins in PostgreSQL Explained

Search online

If this article doesn't have the information you need you can try searching online. Remember, you can contribute suggestions to this page.