Re: Wait event names mismatch: oldserxid - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Wait event names mismatch: oldserxid
Date
Msg-id 20180209135327.GC29003@paquier.xyz
Whole thread Raw
In response to Wait event names mismatch: oldserxid  (Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>)
Responses Re: Wait event names mismatch: oldserxid  (Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>)
Re: Wait event names mismatch: oldserxid  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On Fri, Feb 09, 2018 at 06:04:39PM +0530, Ashutosh Bapat wrote:
> Name for wait event "LWTRANCHE_OLDSERXID_BUFFERS" is printed as
> "oldserxid", but documentation at
> https://www.postgresql.org/docs/10/static/monitoring-stats.html does
> not have exact same event there. Instead it has
>
> OldSerXidLock     Waiting to read or record conflicting serializable
> transactions.

I see two events defined here in the code of type LWLock dedicated to
oldserxid:
- OldSerXidLock which is a wait event defined as it is part of
LWLockNames.
- oldserxid, which gets defined in SimpleLruInit(), which itself calls
LWLockRegisterTranche() to define a second event of type LWLock.

So the docs look correct to me on this side.  What I find weird is the
phrasing to define oldserxid.  Instead of that, the current description:
Waiting to I/O on an oldserxid buffer.
I would suggest "waiting *for* I/O"

A small patch is attached.

Thanks,
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: [HACKERS] Vacuum: allow usage of more than 1GB of work mem
Next
From: Tomas Vondra
Date:
Subject: Re: [HACKERS] FOSDEM PGDay_2018_Developer_Meeting notes