From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
---|---|
To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
Cc: | Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>, Josh Berkus <josh(at)agliodbs(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Subject: | Re: postgresql.conf archive_command example |
Date: | 2011-09-07 02:11:54 |
Message-ID: | CAHGQGwFj8cw0csEs6-3VwQE_vm7gyomZJNQYkHAsZj6PCQFx4Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sat, Sep 3, 2011 at 5:10 AM, Kevin Grittner
<Kevin(dot)Grittner(at)wicourts(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Andy Colson | 2011-09-07 02:58:48 | REVIEW Single pass vacuum - take 2 |
Previous Message | Fujii Masao | 2011-09-07 01:44:27 | Re: Cascaded standby message |