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 <vi...@khera.org> wrote: > On Wed, Nov 24, 2010 at 12:52 PM, DM <dm.a...@gmail.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@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-general > -- View my Linkedin profile <http://uk.linkedin.com/in/matthewdwalden>
