| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Alexey Bashtanov <bashtanov(at)imap(dot)cc> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: How to prioritise walsender reading from pg_wal over WAL writes? |
| Date: | 2020-11-18 16:20:58 |
| Message-ID: | 6a3a9ef99167a7baeaeee3d3df4af59694277e36.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Wed, 2020-11-18 at 12:15 +0000, Alexey Bashtanov wrote:
> My reply did not get threaded appropriately.
> My original question was here:
> https://www.postgresql.org/message-id/a74d5732-60fd-d18b-05fd-7b2b97099f19%40imap.cc
> I'd like to prioritize walsender for replication not to lag too much.
> Otherwise, when I have load spikes on master, standby lags, sometimes by
> hundreds of gigabytes.
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?
Check the difference between "sent_lsn", "replay_lsn" from "pg_stat_replication" and
pg_current_wal_lsn() on the primary.
Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Frits Jalvingh | 2020-11-19 11:52:42 | Re: Postgres using nested loops despite setting enable_nestloop to false |
| Previous Message | Alexey Bashtanov | 2020-11-18 12:15:11 | Re: How to prioritise walsender reading from pg_wal over WAL writes? |