Postgres Pro
Downloads
Home   >   mailing lists

Re: Do sys logger and stats collector need wait events WAIT_EVENT_SYSLOGGER_MAIN/_PGSTAT_MAIN? - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Do sys logger and stats collector need wait events WAIT_EVENT_SYSLOGGER_MAIN/_PGSTAT_MAIN?
Date
Msg-id YawNe3SYoO3F1mJx@paquier.xyz
Whole thread Raw
In response to Do sys logger and stats collector need wait events WAIT_EVENT_SYSLOGGER_MAIN/_PGSTAT_MAIN?  (Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>)
List pgsql-hackers
Tree view 
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
Attachment

pgsql-hackers by date:

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