pgsql: Use posix_fallocate() for new WAL files, where available.

From: Jeff Davis <jdavis(at)postgresql(dot)org>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Use posix_fallocate() for new WAL files, where available.
Date: 2013-07-05 19:33:57
Message-ID: E1UvBlV-0005CQ-LL@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Use posix_fallocate() for new WAL files, where available.

This function is more efficient than actually writing out zeroes to
the new file, per microbenchmarks by Jon Nelson. Also, it may reduce
the likelihood of WAL file fragmentation.

Jon Nelson, with review by Andres Freund, Greg Smith and me.

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/269e780822abb2e44189afaccd6b0ee7aefa7ddd

Modified Files
--------------
configure | 3 +-
configure.in | 2 +-
src/backend/access/transam/xlog.c | 93 +++++++++++++++++++++++--------------
src/include/pg_config.h.in | 3 ++
src/include/pg_config.h.win32 | 3 ++
5 files changed, 67 insertions(+), 37 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Noah Misch 2013-07-05 19:38:21 pgsql: Update messages, comments and documentation for materialized vie
Previous Message Magnus Hagander 2013-07-05 14:26:19 Re: pgsql: Expose the estimation of number of changed tuples since last ana