Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1XJn4V-0005DQ-EL for pgsql-docs@arkaria.postgresql.org; Tue, 19 Aug 2014 17:19:47 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1XJn4U-0007pV-Ur for pgsql-docs@arkaria.postgresql.org; Tue, 19 Aug 2014 17:19:46 +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 1XJn4U-0007pK-Cm for pgsql-docs@postgresql.org; Tue, 19 Aug 2014 17:19:46 +0000 Received: from 01.zmailcloud.com ([192.198.85.104] helo=mx-out-1.zmailcloud.com) by magus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1XJn4P-0006qm-Vs for pgsql-docs@postgresql.org; Tue, 19 Aug 2014 17:19:45 +0000 Received: from smtp.01.com (smtp.01.com [10.10.0.43]) by mx-out-1.zmailcloud.com (Postfix) with ESMTP id 411045643D3; Tue, 19 Aug 2014 12:19:40 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by smtp-out-1.01.com (Postfix) with ESMTP id 22B97A03EE; Tue, 19 Aug 2014 12:19:40 -0500 (CDT) X-Virus-Scanned: amavisd-new at smtp-out-1.01.com Received: from smtp.01.com ([127.0.0.1]) by localhost (smtp-out-1.01.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gf7DAqBpBCG4; Tue, 19 Aug 2014 12:19:40 -0500 (CDT) Received: from smtp.01.com (localhost [127.0.0.1]) by smtp-out-1.01.com (Postfix) with ESMTP id E07A6A03B3; Tue, 19 Aug 2014 12:19:39 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by smtp-out-1.01.com (Postfix) with ESMTP id C40FDA03ED; Tue, 19 Aug 2014 12:19:39 -0500 (CDT) X-Virus-Scanned: amavisd-new at smtp-out-1.01.com Received: from smtp.01.com ([127.0.0.1]) by localhost (smtp-out-1.01.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id rdtGVw0cMiko; Tue, 19 Aug 2014 12:19:39 -0500 (CDT) Received: from [172.47.23.104] (70-36-143-82.dsl.dynamic.sonic.net [70.36.143.82]) by smtp-out-1.01.com (Postfix) with ESMTPSA id 11014A03B3; Tue, 19 Aug 2014 12:19:37 -0500 (CDT) Message-ID: <53F38726.2040804@agliodbs.com> Date: Tue, 19 Aug 2014 10:19:34 -0700 From: Josh Berkus Organization: PostgreSQL Experts Inc. User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: Tom Lane CC: Magnus Hagander , Kevin Grittner , Peter Eisentraut , MauMau , "pgsql-docs@postgresql.org" Subject: Re: Sample archive_command is still problematic References: <53E5603B.5040102@agliodbs.com> <1407777686.41146.YahooMailNeo@web122306.mail.ne1.yahoo.com> <0F73426A2EA544878BCAC33BB989D671@maumau> <53EBCCEA.3090604@gmx.net> <1407965034.12878.YahooMailNeo@web122304.mail.ne1.yahoo.com> <53F233E1.3030605@agliodbs.com> <5718.1408383072@sss.pgh.pa.us> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -1.9 (-) 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 On 08/18/2014 10:31 AM, Tom Lane wrote: > Josh Berkus writes: >> 2) One reason users are using the "test -f" version of the archive >> command is that we put it in the same postgresql.conf. I would suggest >> that we don't put *any* archive command in the sample postgresql.conf, >> since there is no command we can supply which isn't a potential foot-gun. > > If you want to remove the last line of this: > > #archive_command = '' # command to use to archive a logfile segment > # placeholders: %p = path of file to archive > # %f = file name only > # e.g. 'test ! -f /mnt/server/archivedir/%f && cp %p /mnt/server/archivedir/%f' > > I'm okay with that. But if you want to remove the sample command from the > SGML docs I'm going to push back a bit harder... Well, if we want a sample command in the docs, then we should actually give a few different sample commands and even a sample shell script. If we give the users several alternatives, maybe they'll actually think about it instead of just C&P. Make sense? -- Josh Berkus PostgreSQL Experts Inc. http://pgexperts.com -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs