From: | Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com> |
---|---|
To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Wait event names mismatch: oldserxid |
Date: | 2018-02-09 12:34:39 |
Message-ID: | CAFjFpRcmeRsdgT7Mf8F_v4NZVhT4yvSJbrGn7WGZRZjvat6mCw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
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.
Are they same. In that case, should we change the documentation or
code in OldSerXidInit()
808 SimpleLruInit(OldSerXidSlruCtl, "oldserxid",
809 NUM_OLDSERXID_BUFFERS, 0, OldSerXidLock, "pg_serial",
810 LWTRANCHE_OLDSERXID_BUFFERS);
--
Best Wishes,
Ashutosh Bapat
EnterpriseDB Corporation
The Postgres Database Company
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Langote | 2018-02-09 12:36:32 | Re: [HACKERS] path toward faster partition pruning |
Previous Message | Claudio Freire | 2018-02-09 12:20:32 | Re: [HACKERS] Vacuum: allow usage of more than 1GB of work mem |