Re: Sample archive_command is still problematic

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: MauMau <maumau307(at)gmail(dot)com>, Kevin Grittner <kgrittn(at)ymail(dot)com>, pgsql-docs(at)postgresql(dot)org
Subject: Re: Sample archive_command is still problematic
Date: 2014-08-13 18:16:44
Message-ID: 53EBAB8C.40305@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

On 08/11/2014 03:23 PM, MauMau wrote:
> From: "Kevin Grittner" <kgrittn(at)ymail(dot)com>
> The problem with the recommended command is that cp is not atomic.
> The file can be read before the contents are materialized, causing
> early end to recovery. I have seen it happen. The right way to do
> this is to copy to a different name or directory and mv the file
> into place once it is complete -- or use software which does that
> automatically, like rsync does.
>
>
> I submitted a patch a patch for this a few months ago, which is pg_copy
> listed in the current CF. The patch also addresses the problem that the
> archived file can get lost after power failure because it is not flushed
> to disk. The patch consists of a program called pg_copy which can be
> used instead of cp/copy, and a doc fix to suggest using mv. I made it
> following the favorable suggestions from people.

Yah? Does it work on Windows?

--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Peter Eisentraut 2014-08-13 20:39:06 Re: Sample archive_command is still problematic
Previous Message MauMau 2014-08-11 22:23:41 Re: Sample archive_command is still problematic