Re: Monitoring Replication - Postgres 9.2
От | Patrick B |
---|---|
Тема | Re: Monitoring Replication - Postgres 9.2 |
Дата | |
Msg-id | CAJNY3ivh0EdUddHygsZwpOLdCxYHEox-vq3+8hdWfE5e4evSCQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Monitoring Replication - Postgres 9.2 (John R Pierce <pierce@hogranch.com>) |
Ответы |
Re: Monitoring Replication - Postgres 9.2
Re: Monitoring Replication - Postgres 9.2 |
Список | pgsql-general |
2016-11-30 14:21 GMT+13:00 John R Pierce <pierce@hogranch.com>:
On 11/29/2016 5:10 PM, Patrick B wrote:Yep.. once a minute or so. And yes, I need to store a history with timestamp.Any idea? :)so create a table with a timestamptz, plus all the fields you want, have a script (perl? python? whatever your favorite poison is with database access) that once a minute executes those two queries (you'll need two database connections since only the slave knows how far behind it is), and inserts the data into your table.
-- john r pierce, recycling bits in santa cruz
Can't I do it on the DB size? Using a trigger maybe? instead of using Cron?
Patrick
В списке pgsql-general по дате отправления: