From: | François Beausoleil <francois(at)teksol(dot)info> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | replay_location meaning in pg_stat_replication |
Date: | 2012-03-08 05:36:37 |
Message-ID: | 1BB7DC015D714A189C2C0A4326BF148E@ftml.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi all,
I'm just wondering what the numbers really mean. The output is "2FA/B3AFB890", for example. Do these numbers represent something meaningful I can use? Bytes, offsets within files, what? How do you monitor the difference between write_location and replay_location? It seems obvious the values are hex. Anybody has code they want to share?
Section 25.2.5.2 in the 9.1 docs states:
You can retrieve a list of WAL sender processes via the pg_stat_replication (http://www.postgresql.org/docs/9.1/static/monitoring-stats.html#MONITORING-STATS-VIEWS-TABLE) view. Large differences between pg_current_xlog_location and sent_location field might indicate that the master server is under heavy load, while differences between sent_location and pg_last_xlog_receive_location on the standby might indicate network delay, or that the standby is under heavy load.
What is a "large difference" in this context?
Thanks!
François
From | Date | Subject | |
---|---|---|---|
Next Message | hubert depesz lubaczewski | 2012-03-08 07:46:20 | Timeline switch after rsync of *offline* pgdata? |
Previous Message | Aleksey Tsalolikhin | 2012-03-08 05:24:46 | Re: Re: A 154 GB table swelled to 527 GB on the Slony slave. How to compact it? |