Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1XHlk4-0006Ie-N4 for pgsql-docs@arkaria.postgresql.org; Thu, 14 Aug 2014 03:30:20 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1XHlk4-0005Ol-7M for pgsql-docs@arkaria.postgresql.org; Thu, 14 Aug 2014 03:30:20 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1XHlk3-0005ON-JG for pgsql-docs@postgresql.org; Thu, 14 Aug 2014 03:30:19 +0000 Received: from mail-pd0-x22a.google.com ([2607:f8b0:400e:c02::22a]) by makus.postgresql.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1XHljt-00067r-CI for pgsql-docs@postgresql.org; Thu, 14 Aug 2014 03:30:17 +0000 Received: by mail-pd0-f170.google.com with SMTP id g10so793541pdj.29 for ; Wed, 13 Aug 2014 20:30:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:from:to:references:in-reply-to:subject:date:mime-version :content-type:content-transfer-encoding; bh=Pt52UYdacqhJAM3v4tTJ9BN/i7P13Gf6jZrttJp6cUY=; b=Wu0/3ESa5k4UdR2rLZ5ERhtrRQplTQAnHgkl6aj/KivNvAJlb11vCORkW75xe/P5Np NHCY+i9YhF7miBU0URNMN8XbTe+h/4WL+0CCB0LnNpdKrVGU6pYU+Ckt18oPBTVufrzp zty5j0/aJb9F/2scpPEIusLmr37z9oxF0D38FzEe01C33OMnp1pJoYtFM4imCxXcIYLA ypICZkIYkj8pmYHL22o5QBTg/Zq/Yjbtn1GuvzqOOowhO9nTtXkw9ABKu+zIdJkYtTA1 16jHbaR5YEtJnPUHRx1sOsmKnciro2oUgnmsSffx5EbnuLQgGKK0Rsd4+SvKTIyYHUZ4 icQw== X-Received: by 10.70.9.195 with SMTP id c3mr7526624pdb.21.1407987007952; Wed, 13 Aug 2014 20:30:07 -0700 (PDT) Received: from maumau (p23196-ipngn100307sizuokaden.shizuoka.ocn.ne.jp. [153.131.144.196]) by mx.google.com with ESMTPSA id o10sm5478453pdn.41.2014.08.13.20.30.05 for (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 13 Aug 2014 20:30:06 -0700 (PDT) Message-ID: <52795FDC88C44C24B7356C4640B4ED8F@maumau> From: "MauMau" To: "Josh Berkus" , "Kevin Grittner" , References: <53E5603B.5040102@agliodbs.com> <1407777686.41146.YahooMailNeo@web122306.mail.ne1.yahoo.com> <0F73426A2EA544878BCAC33BB989D671@maumau> <53EBAB8C.40305@agliodbs.com> In-Reply-To: <53EBAB8C.40305@agliodbs.com> Subject: Re: Sample archive_command is still problematic Date: Thu, 14 Aug 2014 12:32:47 +0900 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="UTF-8"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Windows Mail 6.0.6002.18197 X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6002.18463 X-Pg-Spam-Score: 0.6 (/) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-docs Precedence: bulk Sender: pgsql-docs-owner@postgresql.org From: "Josh Berkus" > Yah? Does it work on Windows? Yes. pg_copy is meant to be a replacement for cp/copy, not for the entire archive_command script. It just opens, reads, writes, syncs, and closes the file. Regards MauMau -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs