| 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 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2011-09-02 17:13:46 | Re: postgresql.conf archive_command example |
| Previous Message | Andrew Dunstan | 2011-09-02 17:10:14 | Re: postgresql.conf archive_command example |