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

Re: postgresql.conf archive_command example

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Robert Haas" <robertmhaas(at)gmail(dot)com>
Cc: "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 17:10:48
Message-ID: 4E60C7C80200002500040B4D@gw.wicourts.gov (view raw or flat)
Thread:
Lists: pgsql-hackers
Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
 
> maybe instead of shipping a more complicated script we should be
> trying to eliminate (or at least reduce) the need for a more
> complicated script.
 
That was the intent of my pg_archiveto suggestion.  I'll amend it
(based on other comments) to allow for a URL as an alternative way
to specify the directory.  So your archive_command might be:
 
'pg_archiveto /var/pgsql/backup/wal/ %p %f'
 
or:
 
'pg_archiveto http://backup-server/mydbserver/wal/ %p %f'
 
or maybe:
 
'pg_archiveto /mnt/someremotedirectory/ %p %f'
 
-Kevin

In response to

pgsql-hackers by date

Next:From: Kevin GrittnerDate: 2011-09-02 17:13:46
Subject: Re: postgresql.conf archive_command example
Previous:From: Andrew DunstanDate: 2011-09-02 17:10:14
Subject: Re: postgresql.conf archive_command example

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