Re: fallocate / posix_fallocate for new WAL file creation (etc...) - Mailing list pgsql-hackers

From Robert Haas
Subject Re: fallocate / posix_fallocate for new WAL file creation (etc...)
Date
Msg-id CA+TgmoadBa41kFx_J=PPg_k_yCB=cVbkF7QVupN-j8O6j+aUDw@mail.gmail.com
Whole thread Raw
In response to Re: fallocate / posix_fallocate for new WAL file creation (etc...)  (Stephen Frost <sfrost@snowman.net>)
List pgsql-hackers
On Tue, Jun 11, 2013 at 12:58 PM, Stephen Frost <sfrost@snowman.net> wrote:
> * Merlin Moncure (mmoncure@gmail.com) wrote:
>> It's understood that posix_fallocate is faster at this -- the question
>> on the table is 'does this matter in context of postgres?'.
>> Personally I think this patch should go in regardless -- the concerns
>> made IMNSHO are specious.
>
> I've not had a chance to look at this patch, but I tend to agree with
> Merlin.

I also think this is a good idea.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Server side lo-funcs name
Next
From: Robert Haas
Date:
Subject: Re: Hard limit on WAL space used (because PANIC sucks)