Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1er7MM-0004kH-44 for pgsql-admin@arkaria.postgresql.org; Wed, 28 Feb 2018 19:25:50 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1er7ML-0008Gx-3o for pgsql-admin@arkaria.postgresql.org; Wed, 28 Feb 2018 19:25:49 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1er7MK-0008Go-PO for pgsql-admin@lists.postgresql.org; Wed, 28 Feb 2018 19:25:48 +0000 Received: from shopzeus.com ([87.229.70.149]) by makus.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1er7MI-0000Sy-By for pgsql-admin@lists.postgresql.org; Wed, 28 Feb 2018 19:25:47 +0000 Received: from [127.127.127.127] (localhost [127.127.127.127]) (Authenticated sender: gandalf) by shopzeus.com (Postfix) with ESMTPSA id 5ACFB889B83C; Wed, 28 Feb 2018 13:23:14 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=shopzeus.com; s=shopzeus_com; t=1519842194; bh=0FGluDtU5UngbNl6ZDfs5BbrUD1f0cjdeNsu8OdVb9c=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=WL/Jzl7Pol3RZ0EqXWSKfmGOU75LjpgJFDV5TtIxskVbgpLtX3rJ9j4cH0foITzJK EqfvRxTVulis5NCWL2A6kvwYT7oejiGyPqnS95f2XJf4rcFaVAeH03kvLMrVKpOsO5 tqibBeup53c+cYH8Jj8m9oqBizh0nD3ei3Q7B3wb4Tc2SJ+Awu7xbrAJ70/QAzDpLY Hbdqz5Wk2OYbKNkXgX3R5kI03ggr1V3F8kBdDvMZ8+qWOgkHWt7yQ38+BeNXxqzfdq VydsdwF7MxCVmrfoEQSIdyajea8N3fwlqTG9E6dbbeRejFWFMPMkM9kkLEH4ZVkbkQ DuZDzJ8HNqw/g== Subject: Re: Reliable WAL file shipping over unreliable network To: scott ribe Cc: Rui DeSousa , pgsql-admin@lists.postgresql.org References: <400AC9CD-1E43-422C-A689-70BDBAFF231E@elevated-dev.com> <954e01b6-b240-eb9a-5feb-8efd202fef5a@shopzeus.com> <9BE48599-5417-42BF-A7D3-554590878841@elevated-dev.com> <45F65094-CF9C-4BC4-AF56-2FE299F79EFF@icloud.com> From: =?UTF-8?Q?Nagy_L=c3=a1szl=c3=b3_Zsolt?= Message-ID: Date: Wed, 28 Feb 2018 20:25:45 +0100 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-Language: hu List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk > By default the files are placed into a directory named "= =2E~tmp~" > in each file's destination directory, but if you've sp= ecified > the --partial-dir option, that directory will be used i= nstead. > See the comments in the --partial-dir section for a dis= cussion > of how this ".~tmp~" dir will be excluded from the transf= er, and > what you can do if you wnat rsync to cleanup old ".~tmp= ~" dirs > that might be lying around. Conflicts with --inpla= ce and > --append. I stand corrected. It is there. But still: this is a general behaviour of rsync that is independent of most command line options. And yet, "the temporary file" is just an unexplained term that appears in the middle of the description of a (rarely used) option, and the "renamed only after the transfer has completed" part is completely missing. That said, it is just an excuse on my side. I should have figured it out. :-)