From: | Matthew Walden <matthew(dot)walden(at)bcs(dot)org> |
---|---|
To: | Vick Khera <vivek(at)khera(dot)org> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Postgres 9.01 and WAL files issue |
Date: | 2010-11-25 14:56:30 |
Message-ID: | AANLkTikk5kidBQU6me7GpPJ8sLR3kEmheLOPL097_s27@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I thought that when I first read about WAL archiving but the documentation
explains quite well. Basically it is to stop a successful result being
returned in the event that the file already exists in the archive
destination (to cause an error in the event it tries to overwrite a file).
On Thu, Nov 25, 2010 at 2:43 PM, Vick Khera <vivek(at)khera(dot)org> wrote:
> On Wed, Nov 24, 2010 at 12:52 PM, DM <dm(dot)aeqa(at)gmail(dot)com> wrote:
> > Here is my Archive Command:
> > archive_command = 'cp -i %p /mnt/nfs/primary/%f < /dev/null'
> >
>
> Just curious... why would you turn on the interactive version of cp
> for an automated script? Is that why you feed it /dev/null as input?
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>
--
View my Linkedin profile <http://uk.linkedin.com/in/matthewdwalden>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-11-25 15:54:15 | Re: Use of search path in plpgsql functions, PG 8.3.12 |
Previous Message | Vick Khera | 2010-11-25 14:43:15 | Re: Postgres 9.01 and WAL files issue |