Re: Hard limit on WAL space used (because PANIC sucks) - Mailing list pgsql-hackers

From Joshua D. Drake
Subject Re: Hard limit on WAL space used (because PANIC sucks)
Date
Msg-id 51B668CB.8060000@commandprompt.com
Whole thread Raw
In response to Re: Hard limit on WAL space used (because PANIC sucks)  (Josh Berkus <josh@agliodbs.com>)
List pgsql-hackers
On 06/10/2013 04:42 PM, Josh Berkus wrote:

>> Actually we describe what archive_command needs to fulfill, and tell them
>> to use something that accomplishes that.  The example with cp is explicitly
>> given as an example, not a recommendation.
>
> If we offer cp as an example, we *are* recommending it.  If we don't
> recommend it, we shouldn't have it as an example.
>
> In fact, if we don't recommend cp, then PostgreSQL should ship with some
> example shell scripts for archive commands, just as we do for init scripts.

Not a bad idea. One that supports rsync and another that supports 
robocopy. That should cover every platform we support.

JD



-- 
Command Prompt, Inc. - http://www.commandprompt.com/  509-416-6579
PostgreSQL Support, Training, Professional Services and Development
High Availability, Oracle Conversion, Postgres-XC, @cmdpromptinc
For my dreams of your image that blossoms   a rose in the deeps of my heart. - W.B. Yeats



pgsql-hackers by date:

Previous
From: Daniel Farina
Date:
Subject: Re: Hard limit on WAL space used (because PANIC sucks)
Next
From: Michael Paquier
Date:
Subject: Re: how to find out whether a view is updatable