Re: Streaming replication status - Mailing list pgsql-hackers

From Josh Berkus
Subject Re: Streaming replication status
Date
Msg-id 4B4A5F4A.3010501@agliodbs.com
Whole thread Raw
In response to Re: Streaming replication status  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
> Currently there is no way of knowing what the average/current transit
> time is on replication, no way of knowing what is happening if we go
> idle etc.. Those things need to be included because they are not
> otherwise accessible. Cars need windows, not just a finely tuned engine.

Like I said, I agree.  I'm just pointing out that the monitoring
deficiency already exists whether or not we add a max_* parameter.

--Josh Berkus



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Typed tables
Next
From: Andrew Dunstan
Date:
Subject: Re: Feature patch 1 for plperl [PATCH]