|From:||Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>|
|To:||Simon Riggs <simon(at)2ndQuadrant(dot)com>|
|Cc:||Josh Berkus <josh(at)agliodbs(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>|
|Subject:||Re: Streaming replication status|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
Simon Riggs wrote:
> On Fri, 2010-01-08 at 14:20 -0800, Josh Berkus wrote:
>> On 1/8/10 1:16 PM, Heikki Linnakangas wrote:
>>> * A standby that connects to master, initiates streaming, and then sits
>>> idle without stalls recycling of old WAL files in the master. That will
>>> eventually lead to a full disk in master. Do we need some kind of a
>>> emergency valve on that?
>> WARNING: I haven't thought about how this would work together with HS yes.
> I've been reviewing things as we go along, so I'm not that tense
> overall. Having said that I don't understand why the problem above would
> occur and the sentence seems to be missing a verb between "without" and
> "stalls". More explanation please.
Yeah, that sentence was broken.
> What could happen is that the standby could slowly lag behind master.
Right, that's what I'm worried about. In the worst case it the
walreceiver process in the standby might stall completely for some
reason, e.g hardware problem or SIGSTOP by an administrator.
> 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).
|Next Message||Magnus Hagander||2010-01-10 16:43:27||Re: [PATCH] Windows x64 [repost]|
|Previous Message||Boszormenyi Zoltan||2010-01-10 16:35:41||Re: ECPG patch causes warning|