I've gotten a wide variety of feedback on the proposed patch. The comments range from rough approval through various discussion about alternative solutions. At this point I am unsure if this patch is rejected or if it would be accepted once I had the updated man page changes that were discussed last week.
I have attached an updated patch which does incorporate man page changes, in case that is the blocker. However, if this patch is simply rejected, I'd appreciate it if I could get a definitive statement to that effect. Thanks, Jerry On Tue, Jun 26, 2018 at 7:35 AM, Jerry Jelinek <jerry.jeli...@joyent.com> wrote: > Hello All, > > Attached is a patch to provide an option to disable WAL recycling. We have > found that this can help performance by eliminating read-modify-write > behavior on old WAL files that are no longer resident in the filesystem > cache. The is a lot more detail on the background of the motivation for > this in the following thread. > > https://www.postgresql.org/message-id/flat/CACukRjO7DJvub8e2AijOayj8BfKK3 > XXBTwu3KKARiTr67M3E3w%40mail.gmail.com#CACukRjO7DJvub8e2AijOayj8BfKK3 > xxbtwu3kkaritr67m3...@mail.gmail.com > > A similar change has been tested against our 9.6 branch that we're > currently running, but the attached patch is against master. > > Thanks, > Jerry > >
0001-option-to-disable-WAL-recycling.patch
Description: Binary data
