Re: Logging parallel worker draught

From: solai v <solai(dot)cdac(at)gmail(dot)com>
To: Benoit Lobréau <benoit(dot)lobreau(at)dalibo(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Logging parallel worker draught
Date: 2026-06-08 11:34:56
Message-ID: CAF0whuequeH1NkC=iZihRzB_42tm6_NhnLeVeRQCLNCX4bwOdg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jun 8, 2026 at 12:47 PM Benoit Lobréau
<benoit(dot)lobreau(at)dalibo(dot)com> wrote:
>
> This is the v11 of the patch (rebase).

Hi,

I tested the latest v11 patch series on the current master.
Before applying the patches, I was able to reproduce the worker
shortage scenario by running a parallel query that planned 2 workers
but launched only 1 worker. The EXPLAIN ANALYZE output showed:
Workers Planned: 2
Workers Launched: 1
I then applied:
v11-0001-Add-a-guc-for-parallel-worker-logging.patch
v11-0002-Implements-logging-for-parallel-worker-usage-in-util.patch
v11-0003-Implements-logging-for-parallel-worker-usage-in-quer.patch
The patches applied cleanly, but PostgreSQL failed to build.The build
errors indicate that log_parallel_workers,
log_parallel_workers_options, LOG_PARALLEL_WORKERS_NONE, and
LogParallelWorkersIfNeeded() are referenced during compilation but
could not be found, resulting in build failures in several files
including execMain.c, vacuumparallel.c, nbtsort.c, brin.c, and
gininsert.c.
Because of the build failure, I was unable to proceed with runtime testing.
Could you please clarify if there is any additional patch that needs
to be applied, or if I may have missed any step while testing?

Regards,
Solai

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message vignesh C 2026-06-08 11:35:33 Re: Proposal: Conflict log history table for Logical Replication
Previous Message Akshay Joshi 2026-06-08 11:30:32 Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements