| From: | "Godfrin, Philippe E" <philippe(dot)godfrin(at)nov(dot)com> |
|---|---|
| To: | <don(at)seiler(dot)us>, <laurenz(dot)albe(at)cybertec(dot)at> |
| Cc: | <pgsql-admin(at)postgresql(dot)org> |
| Subject: | RE: [EXTERNAL] Re: WALWriteLocks |
| Date: | 2021-04-29 21:20:03 |
| Message-ID: | SA0PR15MB393305277D4E7BF535F91CA4825F9@SA0PR15MB3933.namprd15.prod.outlook.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Have you thought about commit_delay and siblings?
pg
From: Don Seiler <don(at)seiler(dot)us>
Sent: Thursday, April 29, 2021 11:12 AM
To: laurenz(dot)albe(at)cybertec(dot)at
Cc: pgsql-admin(at)postgresql(dot)org
Subject: [EXTERNAL] Re: WALWriteLocks
Use caution when interacting with this [EXTERNAL] email!
On Thu, Apr 29, 2021 at 1:38 AM Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> wrote:
My gues is that you have too many active client connections, and you are suffering
from contention between the many backends that all want to write WAL.
In that case, use a connection pool to limit the number of active connections.
We do have pgbouncer in place already.
Thanks for the replies so far.
What I really want to know in this case is if there is some other PG operation that accounts for a WALWriteLock wait, or is it always an I/O (write) to the WAL file storage, and we can focus our investigation there?
Don.
--
Don Seiler
www.seiler.us
| From | Date | Subject | |
|---|---|---|---|
| Next Message | james terris | 2021-04-30 01:39:36 | FATAL error in logs: no pb_hba.conf entry |
| Previous Message | Vijaykumar Jain | 2021-04-29 20:04:08 | Re: WALWriteLocks |