Skip site navigation (1) Skip section navigation (2)

Re: postgresql.conf archive_command example

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>, Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: postgresql.conf archive_command example
Date: 2011-09-02 19:38:31
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On Fri, Sep 2, 2011 at 3:29 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> Another thought I have here is to wonder whether we should change
>> something on the server side so that we don't NEED such a complicated
>> archive_command.  I mean, copying a file to a directory somewhere is
>> not fundamentally a complex operation.  Nor is using ssh to copy it to
>> another machine.
> It is once you consider error handling and catering to N combinations of
> user requirements.
> I think the notion that we should get rid of archive_command in favor of
> something more hard-wired is sheer lunacy.  We have a nicely decoupled
> arrangement for dealing with these issues now; why would we want to pull
> them into the server?

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

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

Yep, so let's start with that.

Robert Haas
The Enterprise PostgreSQL Company

In response to


pgsql-hackers by date

Next:From: Kevin GrittnerDate: 2011-09-02 19:40:15
Subject: Re: postgresql.conf archive_command example
Previous:From: Kevin GrittnerDate: 2011-09-02 19:38:30
Subject: Re: CF2011-09

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group