| From: | Andrei Lepikhov <lepihov(at)gmail(dot)com> |
|---|---|
| To: | Benoit Lobréau <benoit(dot)lobreau(at)dalibo(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Cc: | solai(dot)cdac(at)gmail(dot)com, alvherre(at)kurilemu(dot)de |
| Subject: | Re: Logging parallel worker draught |
| Date: | 2026-06-23 13:28:42 |
| Message-ID: | 1a8ad1cc-8e6c-4e97-a8c2-55430b39754f@gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Akshay Joshi | 2026-06-23 13:34:25 | Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements |
| Previous Message | Ilia Evdokimov | 2026-06-23 13:27:28 | Re: Hash-based MCV matching for large IN-lists |