Re: Do sys logger and stats collector need wait events WAIT_EVENT_SYSLOGGER_MAIN/_PGSTAT_MAIN?

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Do sys logger and stats collector need wait events WAIT_EVENT_SYSLOGGER_MAIN/_PGSTAT_MAIN?
Date: 2021-12-05 00:53:15
Message-ID: YawNe3SYoO3F1mJx@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Dec 03, 2021 at 12:42:47PM -0500, Tom Lane wrote:
> On the whole I'd be inclined to leave it alone. Even if the reporting
> mechanisms aren't able to report these events today, maybe they'll
> be able to do so in future. The context of the stats collector
> process, in particular, seems likely to change.

These come from 6f3bd98, where I am pretty sure that I (or Robert)
defined those values to not have users guess what to pass down to
WaitLatch(), assuming that this may become useful in the future. So
I'd rather leave them be.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2021-12-05 05:27:45 Why doesn't pgstat_report_analyze() focus on not-all-visible-page dead tuple counts, specifically?
Previous Message Michael Paquier 2021-12-05 00:49:45 Re: Remove extra Logging_collector check before calling SysLogger_Start()