From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
---|---|
To: | Sreejith P <sreejith(at)lifetrenz(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Check replication lag |
Date: | 2020-08-06 02:28:11 |
Message-ID: | CA+hUKGK+gHZbZiHy30J_ft2Srywa8WZ314nrCG0e7UukxPeDeA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, Aug 6, 2020 at 7:02 AM Sreejith P <sreejith(at)lifetrenz(dot)com> wrote:
> IN SYNC mode of replication what would be the impact on Master DB server in terms of over all performance ?
The pg_stat_replication columns write_lag, flush_lag and replay_lag
are designed tell you how long to expect commits to take for
synchronous standbys, based on recent history, if synchronous_commit
it set to remote_write, on or remote_apply respectively. Those times
tell you about commit latency, which limits sequential commit rate for
each session.
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2020-08-06 02:39:42 | Re: [EXTERNAL] RE: PostgreSQL-12 replication. Check replication lag |
Previous Message | Rama Krishnan | 2020-08-06 02:22:03 | Re: Doubt in pgbase |