From: Tom Lane <tgl@sss.pgh.pa.us>
To: pgsql-hackers@postgresql.org, Bruce Momjian <bruce@momjian.us>
Cc: Greg Smith <gsmith@gregsmith.com>
Cc: PostgreSQL-patches <pgsql-patches@postgresql.org>
Subject: Re: [PERFORM] Direct I/O issues
Date: Fri, 24 Nov 2006 14:08:34 -0500
Message-ID: <8864.1164395314@sss.pgh.pa.us> (raw)
In-Reply-To: <200611241858.kAOIwjh23094@momjian.us>
References: <200611241858.kAOIwjh23094@momjian.us>
Bruce Momjian <bruce@momjian.us> writes:
> Not sure if people want this for 8.2. I think we can modify
> test_fsync.c anytime but the movement of the defines into an include
> file is a backend code change.
I think fooling with this on the day before RC1 is an unreasonable risk ...
and I disapprove of moving this code into a widely-used include file
like xlog.h, too.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, bruce@momjian.us, gsmith@gregsmith.com, pgsql-patches@postgresql.org
Subject: Re: [PERFORM] Direct I/O issues
In-Reply-To: <8864.1164395314@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox