Re: Monitoring Replication - Postgres 9.2
От | Patrick B |
---|---|
Тема | Re: Monitoring Replication - Postgres 9.2 |
Дата | |
Msg-id | CAJNY3it=PGiKQncUhBbSdfwzX6dWSvo4sShM6M4TXuThRt58tw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Monitoring Replication - Postgres 9.2 (John R Pierce <pierce@hogranch.com>) |
Ответы |
Re: Monitoring Replication - Postgres 9.2
|
Список | pgsql-general |
2016-11-30 14:02 GMT+13:00 John R Pierce <pierce@hogranch.com>:
On 11/29/2016 3:31 PM, Patrick B wrote:I use these queries to monitor the streaming replication:on master:select client_addr, state, sent_location, write_location, flush_location, replay_location, sync_priority from pg_stat_replication;On slave:select now() - pg_last_xact_replay_timestamp() AS replication_delay; Can I create a table to store that data?
sure, why not ? do you want this table to just have one row with the last value you stored? or do you want to store a history with timestamp ?I also need the data is constantly put into this table. How would be the best way to do it?
um, that data changes continuously, what do you mean, 'constantly' ? if you mean once a minute or something, use a script that samples the data and stores it in your table, and waits a minute, then repeats. if you mean literally continously, why not just query the data as you have, thats the 'live' value ... you oculd use a view, I suppose.
-- john r pierce, recycling bits in santa cruz
Yep.. once a minute or so. And yes, I need to store a history with timestamp.
Any idea? :)
Thanks!
В списке pgsql-general по дате отправления: