From: Alexey Bashtanov <bashtanov@imap.cc>
To: Laurenz Albe <laurenz.albe@cybertec.at>
Cc: pgsql-performance@postgresql.org
Subject: Re: How to prioritise walsender reading from pg_wal over WAL writes?
Date: Thu, 19 Nov 2020 13:38:46 +0000
Message-ID: <754ba288-1c2c-a4b4-0fb3-38fbc03053fd@imap.cc> (raw)
In-Reply-To: <6a3a9ef99167a7baeaeee3d3df4af59694277e36.camel@cybertec.at>
References: <774ec1b8-c7c6-cfa2-098d-5c6a32dcfc1a@imap.cc>
<e40e61e6671d02ce79512439054bda9932bef8c1.camel@cybertec.at>
<de2437b8-6de7-b9ce-0835-2d57e989ee30@imap.cc>
<6a3a9ef99167a7baeaeee3d3df4af59694277e36.camel@cybertec.at>
> I would first determine where the bottleneck is.
>
> Is it really the walsender, or is it on the network or in the standby server's replay?
It is really the walsender, and it really is the performance of the WAL
storage on the master.
> Check the difference between "sent_lsn", "replay_lsn" from "pg_stat_replication" and
> pg_current_wal_lsn() on the primary.
Yes I've checked these numbers, the lagging one is sent_lsn.
It doesn't look like it's hitting network capacity either.
When we moved it to an NVMe as a short-term solution it worked fine.
Best, Alex
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: bashtanov@imap.cc, laurenz.albe@cybertec.at
Subject: Re: How to prioritise walsender reading from pg_wal over WAL writes?
In-Reply-To: <754ba288-1c2c-a4b4-0fb3-38fbc03053fd@imap.cc>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox