pg.ddx.io pgsql-hackers@postgresql.org mailing list archive help / color / mirror / Atom feed From: Andrei Lepikhov <lepihov@gmail.com>
To: Benoit Lobréau <benoit.lobreau@dalibo.com>
To: pgsql-hackers <pgsql-hackers@postgresql.org>
Cc: solai.cdac@gmail.com
Cc: alvherre@kurilemu.de
Subject: Re: Logging parallel worker draught
Date: Tue, 23 Jun 2026 15:28:42 +0200
Message-ID: <1a8ad1cc-8e6c-4e97-a8c2-55430b39754f@gmail.com> (raw )
In-Reply-To: <5214af4c-25ab-4fe7-b4be-2ea9e0cb8f30@dalibo.com >
References: <10D5C31A-A303-4440-BCA2-921440A9E1CC@amazon.com >
<63d182f8-1a65-4e34-a335-403f53b14ba7@dalibo.com >
<fd9b82bc-c853-4143-ba8f-35a693ee439c@dalibo.com >
<CAECtzeX+tqQ0gLAiK558MtqLHvBEQM60i2UGSNJ1-QjMRFNYZg@mail.gmail.com >
<31dc1548-30dc-4423-b939-2842c469f129@dalibo.com >
<CAA5RZ0tS=Fmgku9=qCp-U4EBC-dqVtj+v_EGrKV_NA=THnUDsQ@mail.gmail.com >
<82ffc7a2-b77d-437b-a684-4a79a32fd87b@dalibo.com >
<CAA5RZ0srSE487wJMBjs7CmG_nQ3THB_mZVRkFDVuF9sXrhAxhw@mail.gmail.com >
<57c9576f-9689-4667-825d-fd2bec43c793@dalibo.com >
<CAA5RZ0voe52P0BidOJfRWvHU0naitf_z45-7k_NMP7qoOf4DMA@mail.gmail.com >
<e8df9573-b05f-4e8a-ab20-af134b469574@dalibo.com >
<CAA5RZ0tHb_hpq472oMj6S8F5kgXiOE-mV9QYSJOjn4g+CvZXmA@mail.gmail.com >
<CAAKRu_Yu+2ah=G-yeLe04YzCp1FMCpWXBQTXPCy+SArojVVLPw@mail.gmail.com >
<e8b0f127-697a-4d18-a718-1c96425a343b@dalibo.com >
<CAA5RZ0v0uhfAwWJ_hEzSP4aM1Qa6rsLu+2YuyyWXqGHuPaTE0Q@mail.gmail.com >
<a99abd55-267f-48b4-84bc-2892a9e2edc0@dalibo.com >
<5214af4c-25ab-4fe7-b4be-2ea9e0cb8f30@dalibo.com >
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
view thread (53+ messages) latest in thread
Message-ID: <1a8ad1cc-8e6c-4e97-a8c2-55430b39754f@gmail.com>
Permalink: ../1a8ad1cc-8e6c-4e97-a8c2-55430b39754f@gmail.com/
Also on: postgresql.org/message-id/1a8ad1cc-8e6c-4e97-a8c2-55430b39754f@gmail.com
copy link · copy postgr.es
reply Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: lepihov@gmail.com, benoit.lobreau@dalibo.com, solai.cdac@gmail.com, alvherre@kurilemu.de
Subject: Re: Logging parallel worker draught
In-Reply-To: <1a8ad1cc-8e6c-4e97-a8c2-55430b39754f@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox