Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> I wasn't really proposing to get rid of it, but I do wonder if there
> are some configuration parameters we could add somewhere that would
> make common cases easier without making really complex things
> impossible.

I think the solution to that problem is to provide a default archive
command that just does the very simple thing, namely moving the WAL file
to some place given as parameter.  Some “local” mount point.

>> Now, providing a more useful sample script is certainly reasonable.

Allow me to insist here, I don't think a sample is what we need to be
providing our users.  I think they deserve a default production grade
implementation of a very simple archive command.

Regards,
-- 
Dimitri Fontaine
http://2ndQuadrant.fr     PostgreSQL : Expertise, Formation et Support

In response to

• Re: postgresql.conf archive_command example at 2011-09-02 19:38:31 from Robert Haas

Responses

• Re: postgresql.conf archive_command example at 2011-09-02 20:10:30 from Kevin Grittner

pgsql-hackers by date

Next:	From: Tomas Vondra	Date: 2011-09-02 19:52:37
	Subject: Re: PATCH: regular logging of checkpoint progress
Previous:	From: Kevin Grittner	Date: 2011-09-02 19:40:15
	Subject: Re: postgresql.conf archive_command example