| From: | Vijaykumar Jain <vijaykumarjain(dot)github(at)gmail(dot)com> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Don Seiler <don(at)seiler(dot)us> |
| Cc: | pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: WALWriteLocks |
| Date: | 2021-05-24 14:13:15 |
| Message-ID: | CAM+6J96N8SQ_eV1ttdVJmVEyHxz8m96Cp2A4YpZyX3FLf8E2pg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Hey Don,
Was this resolved?
We're there any changes after moving wal to ssd ?
On Wed, May 5, 2021, 10:14 PM Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> wrote:
> 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 | Don Seiler | 2021-05-24 15:05:30 | Re: WALWriteLocks |
| Previous Message | Michel SALAIS | 2021-05-22 07:52:18 | RE: Get stats of deletes ,inserts,trasnactions and updates daily in entire database |