Re: WALWriteLocks
| От | Don Seiler |
|---|---|
| Тема | Re: WALWriteLocks |
| Дата | |
| Msg-id | CAHJZqBDHZyPCXjnOhS2C9YoBTaJ0_e47M_q7pob+F0VT_B48fQ@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: WALWriteLocks (Laurenz Albe <laurenz.albe@cybertec.at>) |
| Ответы |
Re: WALWriteLocks
Re: WALWriteLocks RE: [EXTERNAL] Re: WALWriteLocks |
| Список | pgsql-admin |
On Thu, Apr 29, 2021 at 1:38 AM Laurenz Albe <laurenz.albe@cybertec.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.
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
www.seiler.us
В списке pgsql-admin по дате отправления: