Re: postgresql.conf archive_command example - Mailing list pgsql-hackers

From Fujii Masao
Subject Re: postgresql.conf archive_command example
Date
Msg-id CAHGQGwFj8cw0csEs6-3VwQE_vm7gyomZJNQYkHAsZj6PCQFx4Q@mail.gmail.com
Whole thread Raw
In response to Re: postgresql.conf archive_command example  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Responses Re: postgresql.conf archive_command example
List pgsql-hackers
On Sat, Sep 3, 2011 at 5:10 AM, Kevin Grittner
<Kevin.Grittner@wicourts.gov> wrote:
> (2)  It should copy, not move, with protection against overwriting
> an existing file.

I agree that basically archive_command should not overwrite an existing file.
But if the size of existing file is less than 16MB, it should do that.
Otherwise,
that WAL file would be lost forever.

I have another feature request;
(5) Maybe not in the initial version, but eventually it might be
nice to support calling posix_fadvise(POSIX_FADV_DONTNEED)
after copying a WAL file.

Regards,

--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center


pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Re: Cascaded standby message
Next
From: Andy Colson
Date:
Subject: REVIEW Single pass vacuum - take 2