Re: BUG #15335: Documentation is wrong about archive_command and existing files

From: David Steele <david(at)pgmasters(dot)net>
To: Stephen Frost <sfrost(at)snowman(dot)net>
Cc: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Phil Endecott <spam_from_pgsql_lists(at)chezphil(dot)org>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15335: Documentation is wrong about archive_command and existing files
Date: 2018-08-22 12:35:33
Message-ID: f6b16899-d634-4702-f14c-8c554bf3dbe8@pgmasters.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 8/20/18 9:24 AM, Stephen Frost wrote:
> * David Steele (david(at)pgmasters(dot)net) wrote:
>
>> We could at least list all the things that a good archive command should
>> do and point out that the example in the docs doesn't do them and that
>> it is intended *only* as an example.
>
> This sounds like a good idea to me, in general. I suggest we qualify
> the command shown further and say it's only provided as an illustration
> of how to set an archive_command and that it isn't an example. Perhaps
> we should even remove the shell-script bits and instead just have:
>
> archive_command = 'archivecmd /mnt/server/archivedir/%f %p'

+1

>
> As long as we have something there that looks like valid shell script
> and which doesn't obviously fail, people are likely going to continue to
> use it.

OK -- I'll work up a doc patch that lists the basic things an archive
command should do and see where that leads us.

Regards,
--
-David
david(at)pgmasters(dot)net

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Alexander Kukushkin 2018-08-22 14:30:46 Re: BUG #15346: Replica fails to start after the crash
Previous Message Michael Paquier 2018-08-22 08:11:26 Re: BUG #15346: Replica fails to start after the crash