Re: Logging parallel worker draught - Mailing list pgsql-hackers

From Andrei Lepikhov
Subject Re: Logging parallel worker draught
Date
Msg-id 1a8ad1cc-8e6c-4e97-a8c2-55430b39754f@gmail.com
Whole thread
In response to Re: Logging parallel worker draught  (Benoit Lobréau <benoit.lobreau@dalibo.com>)
Responses Re: Logging parallel worker draught
List pgsql-hackers
On 13/04/2026 11:44, Benoit Lobréau wrote:
> This is the v11 of the patch (rebase).
I wonder, what is the actual reason to report after the operation ended? What if
the operation has been interrupted? We will not see the report at all. Maybe it
is better to do after the launch: we successfully acquired worker slot, and
that's what we actually wanted to know, isn't it?

Also, I don't understand why log_parallel_workers has exactly these options, and
there is no documentation explaining the reasoning. Generally, I'd prefer the
log level here - it would be easier to write tests as well.

-- 
regards, Andrei Lepikhov,
pgEdge



pgsql-hackers by date:

Previous
From: Ilia Evdokimov
Date:
Subject: Re: Hash-based MCV matching for large IN-lists
Next
From: Akshay Joshi
Date:
Subject: Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements