Re: Streaming replication status - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Streaming replication status
Date
Msg-id 1263145254.19367.143332.camel@ebony
Whole thread Raw
In response to Re: Streaming replication status  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Responses Re: Streaming replication status  (Josh Berkus <josh@agliodbs.com>)
List pgsql-hackers
On Sun, 2010-01-10 at 18:40 +0200, Heikki Linnakangas wrote:

> > We
> > don't have any way of monitoring that, as yet. Setting ps display is not
> > enough here.
> 
> Yeah, monitoring would be nice too. But what I was wondering is whether
> we need some way of stopping that from filling the disk in master.
> (Fujii-san's suggestion of a GUC to set the max. amount of WAL to keep
> in the master for standbys feels good to me).

OK, now I got you. I thought that was already agreed; guess it is now.

We need monitoring anywhere we have a max_* parameter. Otherwise we
won't know how close we are to disaster until we hit the limit and
things break down. Otherwise we will have to set parameters by trial and
error, or set them so high they are meaningless.

-- Simon Riggs           www.2ndQuadrant.com



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [PATCH] Windows x64 [repost]
Next
From: Peter Eisentraut
Date:
Subject: Re: damage control mode