From: | Patrick B <patrickbakerbr(at)gmail(dot)com> |
---|---|
To: | John R Pierce <pierce(at)hogranch(dot)com> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Monitoring Replication - Postgres 9.2 |
Date: | 2016-11-30 01:40:34 |
Message-ID: | CAJNY3ivh0EdUddHygsZwpOLdCxYHEox-vq3+8hdWfE5e4evSCQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
2016-11-30 14:21 GMT+13:00 John R Pierce <pierce(at)hogranch(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | John R Pierce | 2016-11-30 01:55:04 | Re: Monitoring Replication - Postgres 9.2 |
Previous Message | John R Pierce | 2016-11-30 01:21:31 | Re: Monitoring Replication - Postgres 9.2 |