On 04/05/2014 08:47 AM, Andy Colson wrote:
Hi All.
I've started using replication, and I'd like to monitor my logs for
any errors or problems. I don't want to do it manually, and I'm not
interested in stats (a la PgBadger).
What I'd like, is the instant PG logs: "FATAL: wal segment already
On Sat, Apr 5, 2014 at 8:47 AM, Andy Colson wrote:
> Hi All.
>
> I've started using replication, and I'd like to monitor my logs for any
> errors or problems. I don't want to do it manually, and I'm not interested
> in stats (a la PgBadger).
>
> What I'd like, is the instant PG logs: "FATAL: wal
General thought:
It's entirely possible my current Postgres environment is missing
something (I'm an automation engineer, not a DBA - most of my postgres
knowledge has been learned on the job or from Google), but we actively
monitor the receive and replay lag (i.e. comparing
pg_current_xlog_lo
Hi All.
I've started using replication, and I'd like to monitor my logs for any errors
or problems. I don't want to do it manually, and I'm not interested in stats
(a la PgBadger).
What I'd like, is the instant PG logs: "FATAL: wal segment already removed" (or
some such bad thing), I'd like
