public inbox for [email protected]  

help / color / mirror / Atom feed

From: Peter Eisentraut <[email protected]>
To: MauMau <[email protected]>
To: Kevin Grittner <[email protected]>
To: Josh Berkus <[email protected]>
To: [email protected]
Subject: Re: Sample archive_command is still problematic
Date: Wed, 13 Aug 2014 16:39:06 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <0F73426A2EA544878BCAC33BB989D671@maumau>
References: <[email protected]>
	<[email protected]>
	<0F73426A2EA544878BCAC33BB989D671@maumau>
List-Unsubscribe: <mailto:[email protected]?body=unsub%20pgsql-docs>

On 8/11/14 6:23 PM, MauMau wrote:
> 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.

I realize that there are about 128 different ways people set this up
(which is itself a problem), but it appears to me that a solution like
pg_copy only provides local copying, which implies the use of something
like NFS.  Which may be OK, but then we'd need to get into the details
of how to set up NFS properly for this.

Also, I think you can get local copy+fsync with dd.

The alternatives of doing remote copying inside archive_command are also
questionable if you have multiple standbys.

Basically, this whole interface is terrible.  Maybe it's time to phase
it out and start looking into pg_receivexlog.



-- 
Sent via pgsql-docs mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs

view thread (25+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Sample archive_command is still problematic
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox