Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1YkzQG-0003wc-Sa for pgsql-hackers@arkaria.postgresql.org; Wed, 22 Apr 2015 18:30:57 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1YkzQG-00007s-8C for pgsql-hackers@arkaria.postgresql.org; Wed, 22 Apr 2015 18:30:56 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1YkzQF-00007i-6b for pgsql-hackers@postgresql.org; Wed, 22 Apr 2015 18:30:55 +0000 Received: from mail-qc0-x232.google.com ([2607:f8b0:400d:c01::232]) by magus.postgresql.org with esmtps (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1YkzQA-0000H1-RD for pgsql-hackers@postgresql.org; Wed, 22 Apr 2015 18:30:53 +0000 Received: by qcpm10 with SMTP id m10so98223074qcp.3 for ; Wed, 22 Apr 2015 11:30:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=OIE4jr7w3+sOH1Dt1ouTx2k84jq7gQZprhCKUa+EhYM=; b=zw4FA4lrB0oauxMSrVSBW8FTbSLfTSJoM5hgk+jm5OBk14nuHN4ECsLVFiiDkHTfTk tgdTonP/F14QPcn0yquKkrmWB7ZTXV7NBA0YnVYeFjo9AgUcb8r+IBSnnv2FT57L0CJH uDjv0j97OFcuxO6Q1lyiJfv5Xsozh5KyGUxktPXn46wld1P0a1P+FAlcBfEC0qbDGDJn Jt/KWEIZPeQfdiF0sW9tQeF8GwMErFbBZylR7AOIzD8CbAVClgycKIh9VWz3rnExZJXa HuGBxwRERKrJiVSNjnB23iJTzvMlZ8R8N0vWov5Id6MbOYGgcxtvZoAECnBr+WPVQiZ7 Y+eg== MIME-Version: 1.0 X-Received: by 10.55.31.85 with SMTP id f82mr51176858qkf.6.1429727448633; Wed, 22 Apr 2015 11:30:48 -0700 (PDT) Received: by 10.140.250.139 with HTTP; Wed, 22 Apr 2015 11:30:48 -0700 (PDT) In-Reply-To: <55373D17.5050706@iki.fi> References: <548AF1CB.80702@vmware.com> <689EB259-44C2-4820-B901-4F6B1C55A1E4@simply.name> <549083D6.1000301@vmware.com> <54949108.3030109@vmware.com> <552FA38F.9060005@iki.fi> <5535FE71.1010905@iki.fi> <55362CAD.2000207@iki.fi> <55373D17.5050706@iki.fi> Date: Wed, 22 Apr 2015 14:30:48 -0400 Message-ID: Subject: Re: Streaming replication and WAL archive interactions From: Robert Haas To: hlinnaka Cc: Michael Paquier , Venkata Balaji N , Andres Freund , Fujii Masao , Borodin Vladimir , PostgreSQL-development Content-Type: text/plain; charset=UTF-8 X-Pg-Spam-Score: -2.7 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org On Wed, Apr 22, 2015 at 2:17 AM, Heikki Linnakangas wrote: > Note that it's a bit complicated to set up that scenario today. Archiving is > never enabled in recovery mode, so you'll need to use a custom cron job or > something to maintain the archive that C uses. The files will not > automatically flow from B to the second archive. With the patch we're > discussing, however, it would be easy: just set archive_mode='always' in B. Hmm, I see. But if C never replays the last, partial segment from the old timeline, how does it follow the timeline switch? -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers