Message-ID: <6e8a24089781301efb1e06d0b0b0924439e10b4a.camel@cybertec.at>
Subject: Re: WALWriteLocks
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Don Seiler <don@seiler.us>, Vijaykumar Jain
	 <vijaykumarjain.github@gmail.com>
Cc: pgsql-admin <pgsql-admin@postgresql.org>
Date: Wed, 05 May 2021 18:44:57 +0200
In-Reply-To: 
 <CAHJZqBBozP4S2DhNGo1hAi_WO2gTzqQoAawWQqNh7CsSQCJOKg@mail.gmail.com>
References: 
	<CAHJZqBDXNEOZDYQXB+xUK2ie-Tjzmn72RHVec-NsCNyU4TeydQ@mail.gmail.com>
	 <63f24de419af530402a16a97c5e5ec977f4092dc.camel@cybertec.at>
	 <CAHJZqBDHZyPCXjnOhS2C9YoBTaJ0_e47M_q7pob+F0VT_B48fQ@mail.gmail.com>
	 <CAM+6J94EyTQLOk8EQ2W8kTnS1Ez5kM9a-udao8U5FggK5_mhdw@mail.gmail.com>
	 <CAM+6J95J=U3LL=bx23WW_6P8naZ=BcoScuhTWG07f423W+ZT6A@mail.gmail.com>
	 <f2fee5feab7766f11814535d4244bb40c18a7b03.camel@cybertec.at>
	 <CAM+6J96M3Sj+eeyFrt2HPQ7VrFojQ1biSM6kC-1mUC_ce-dLWw@mail.gmail.com>
	 <CAM+6J96XOP34eiaERGAT9YupiOfudc-uiHpwtc43t9vOgu=ESQ@mail.gmail.com>
	 <CAHJZqBBozP4S2DhNGo1hAi_WO2gTzqQoAawWQqNh7CsSQCJOKg@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.36.5 (3.36.5-2.fc32) 
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/6e8a24089781301efb1e06d0b0b0924439e10b4a.camel%40cybertec.at>
Precedence: bulk

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