Received: from maia.hub.org (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id D1223632F50 for ; Fri, 12 Feb 2010 11:48:06 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 50392-10 for ; Fri, 12 Feb 2010 15:47:29 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-yw0-f176.google.com (mail-yw0-f176.google.com [209.85.211.176]) by mail.postgresql.org (Postfix) with ESMTP id 1B5D8632C27 for ; Fri, 12 Feb 2010 11:47:56 -0400 (AST) Received: by ywh6 with SMTP id 6so2251700ywh.4 for ; Fri, 12 Feb 2010 07:47:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=WXMJO4Q7bIwVAEXJ+fTeBn6CCIqIACry9Lu4vMQDEb0=; b=BHWg7L61dxK7zyEdHa6Am+GoMabfdZGMg82H1EwPgOceNk2z5XzzlNPw6/Rbp9PxAn g/k48qT6ob9mt1gOvnq5fY+dI8i0Kmx2OtFnnYYNb60SuJT3PhqRI19814NgZtHzVUAT jeiNKSZix0ZWpwvKG2omxWLs8kf0JDNOXnpz8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=o823kOagaftsd8XsiARzYR6iwPwPYQpssYxj4EgNIzoNFv6tX6KBYLABHFpxQrehRs klpMXzCw6v93ev7RbC5LsE0Sj1+XYdbNygxWqSdM2C5y+95sJolt6MvioTmp1OtxfSVY RhdPhI4ZfPRCgAdXIzFxjyVoTcGspHnOsLHUk= MIME-Version: 1.0 Received: by 10.101.194.20 with SMTP id w20mr2169995anp.156.1265989662991; Fri, 12 Feb 2010 07:47:42 -0800 (PST) In-Reply-To: <4B75533D.2000703@enterprisedb.com> References: <20100127152751.3B2047541B9@cvs.postgresql.org> <1265893599.7341.1454.camel@ebony> <877hqjc2kk.fsf@hi-media-techno.com> <1265896250.7341.1627.camel@ebony> <4B740C6C.3010607@enterprisedb.com> <1265897834.7341.1714.camel@ebony> <4B7412BE.5030605@enterprisedb.com> <3f0b79eb1002112138n61a3258fg9986e50751d44ea0@mail.gmail.com> <1265979080.7341.3679.camel@ebony> <4B75533D.2000703@enterprisedb.com> Date: Sat, 13 Feb 2010 00:47:42 +0900 Message-ID: <3f0b79eb1002120747q3203bed6ue1bd07558ec2e38b@mail.gmail.com> Subject: Re: Re: [COMMITTERS] pgsql: Make standby server continuously retry restoring the next WAL From: Fujii Masao To: Heikki Linnakangas Cc: Simon Riggs , Dimitri Fontaine , PostgreSQL-development Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.997 tagged_above=-10 required=5 tests=AWL=0.602, BAYES_00=-2.599 X-Spam-Level: X-Archive-Number: 201002/1021 X-Sequence-Number: 157364 On Fri, Feb 12, 2010 at 10:10 PM, Heikki Linnakangas wrote: >> So I suggest that you have a new action that gets called after every >> checkpoint to clear down the archive. It will remove all files from the >> archive prior to %r. We can implement that as a sequence of unlink()s >> from within the server, or we can just call a script to do it. I prefer >> the latter approach. However we do it, we need something initiated by >> the server to maintain the archive and stop it from overflowing. > > +1 If we leave executing the remove_command to the bgwriter, the restartpoint might not happen unfortunately for a long time. To prevent that situation, the archiver should execute the command, I think. Thought? Regards, -- Fujii Masao NIPPON TELEGRAPH AND TELEPHONE CORPORATION NTT Open Source Software Center