| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Don Seiler <don(at)seiler(dot)us>, Vijaykumar Jain <vijaykumarjain(dot)github(at)gmail(dot)com> |
| Cc: | pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: WALWriteLocks |
| Date: | 2021-05-05 16:44:57 |
| Message-ID: | 6e8a24089781301efb1e06d0b0b0924439e10b4a.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Wed, 2021-05-05 at 11:25 -0500, Don Seiler wrote:
> What I want to know is if there are other events that would contribute
> to a WALWriteLock (eg writing to a data file or the postgresql.log file)
> or is it 100% writing to the WAL file.
You don't contribute to a lock...
The documentation says
(https://www.postgresql.org/docs/13/monitoring-stats.html#WAIT-EVENT-LOCK-TABLE)
> WALWrite Waiting for WAL buffers to be written to disk.
So it is contention while writing or flushing WAL.
You can read the code for the details.
Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Godfrin, Philippe E | 2021-05-06 13:20:45 | RE: [EXTERNAL] timescaledb backup, pg_dump warnings |
| Previous Message | Don Seiler | 2021-05-05 16:25:33 | Re: WALWriteLocks |