Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1YkzrV-0004x9-46 for pgsql-hackers@arkaria.postgresql.org; Wed, 22 Apr 2015 18:59:05 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1YkzrU-00024r-0M for pgsql-hackers@arkaria.postgresql.org; Wed, 22 Apr 2015 18:59:04 +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 1YkzrS-00024d-G9 for pgsql-hackers@postgresql.org; Wed, 22 Apr 2015 18:59:02 +0000 Received: from mail-qk0-x229.google.com ([2607:f8b0:400d:c09::229]) by magus.postgresql.org with esmtps (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1YkzrN-0000mb-30 for pgsql-hackers@postgresql.org; Wed, 22 Apr 2015 18:59:01 +0000 Received: by qkhg7 with SMTP id g7so236236433qkh.2 for ; Wed, 22 Apr 2015 11:58:54 -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=Od2E6S2RMBKssMls1sjm3vlUNRLzqPMDsEjliQqiLKE=; b=FJNlGrCyQqTLTqDrOof9URJnvpHvxcxBF34e2Oll1ESurz45MJ58HlHu6PqpUoIp3Y 3FhABL1H5JxGvnbFlvh0/F+2g1kwEOx/rmlzisz6VobRlpr3MhKG8TZYtCW7FRAOTNYd JX9pSBEQrqpSFjYDbQvP0HwOHUS8GLB0PqHgzrXt7U+pfLLlhu8Tx4p3iJ9ijVDW8mCD ikREyGA0eS+e4Q02P2NF8wokD9/zSluM7MXksR+jw3lpT0OvpgMQZz0dxVzhHa2gdtnl QD9nb/Vi2lUGusIilg8aHUHI6mYTuHU7noj0kCopIO22Y6cotBCR1SxEFeOTHRDgbCdc EGxw== MIME-Version: 1.0 X-Received: by 10.55.48.16 with SMTP id w16mr51702887qkw.13.1429729134862; Wed, 22 Apr 2015 11:58:54 -0700 (PDT) Received: by 10.140.250.139 with HTTP; Wed, 22 Apr 2015 11:58:54 -0700 (PDT) In-Reply-To: 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> Date: Wed, 22 Apr 2015 14:58:54 -0400 Message-ID: Subject: Re: Streaming replication and WAL archive interactions From: Robert Haas To: Michael Paquier Cc: hlinnaka , Venkata Balaji N , Andres Freund , Fujii Masao , Borodin Vladimir , PostgreSQL-development Content-Type: text/plain; charset=UTF-8 X-Pg-Spam-Score: -2.0 (--) 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 Tue, Apr 21, 2015 at 8:30 PM, Michael Paquier wrote: > This .partial segment renaming is something that we > should let the archive_command manage with its internal logic. This strikes me as equivalent to saying "we don't know how to make this work right, but maybe our users will know". That never works out. As things stand, we have a situation where the archive_command examples in our documentation are known to be flawed. They don't fsync the file, and they'll write a partial file and then, when rerun, fail to copy the full file because there's already something there. Efforts have been made to fix these problems (see the pg_copy thread), but they haven't been completed yet, nor have we even documented the issues with the commands recommended by the documentation. Let's please not throw anything else on the pile of things we're expecting users to somehow "get right". -- 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