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

From Melanie Plageman
Subject Re: Logging parallel worker draught
Date
Msg-id CAAKRu_Yu+2ah=G-yeLe04YzCp1FMCpWXBQTXPCy+SArojVVLPw@mail.gmail.com
Whole thread Raw
In response to Re: Logging parallel worker draught  ("Imseih (AWS), Sami" <simseih@amazon.com>)
Responses Re: Logging parallel worker draught
List pgsql-hackers
On Mon, Feb 3, 2025 at 12:37 AM Sami Imseih <samimseih@gmail.com> wrote:
>
> Besides that, I think this is ready for committer.

I started looking at this, and I like the idea.

A few comments: I don't understand what 0002 is. For starters, the
commit message says something about pg_stat_database, and there are no
changes related to that.

Also, we already have basically identical logging coming from
parallel_vacuum_process_all_indexes() and viewable in existing output.
Not only does your implementation not replace this, it is odd that
setting your new guc to none does not disable this. It seems a bit
inconsistent. I'm not sure what the exact right behavior is here,
though.

Since your last update, it seems parallel gin index build has been
committed, so perhaps you want to add that.

- Melanie



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Enhancing Memory Context Statistics Reporting
Next
From: Jacob Champion
Date:
Subject: Re: [PoC] Federated Authn/z with OAUTHBEARER