From: | Greg Smith <gsmith(at)gregsmith(dot)com> |
---|---|
To: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Direct I/O issues |
Date: | 2006-11-23 18:09:54 |
Message-ID: | Pine.GSO.4.64.0611231249410.29593@westnet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches pgsql-performance |
On Thu, 23 Nov 2006, Tom Lane wrote:
> * It does not check for errors (if it had, you might have realized the
> other problem).
All the test_fsync code needs to check for errors better; there have been
multiple occasions where I've run that with quesiontable input and it
didn't complain, it just happily ran and reported times that were almost
0.
Thanks for the note about alignment, I had seen something about that in
the xlog.c but wasn't sure if that was important in this case.
It's very important to the project I'm working on that I get this cleared
up, and I think I'm in a good position to fix it myself now. I just
wanted to report the issue and get some initial feedback on what's wrong.
I'll try to rewrite that code with an eye toward the "Determine optimal
fdatasync/fsync, O_SYNC/O_DSYNC options" to-do item, which is what I'd
really like to have.
--
* Greg Smith gsmith(at)gregsmith(dot)com http://www.gregsmith.com Baltimore, MD
From | Date | Subject | |
---|---|---|---|
Next Message | Neil Conway | 2006-11-23 18:14:44 | Re: 8.2 open items list |
Previous Message | David Fetter | 2006-11-23 18:05:06 | Re: FKs + partial indexes? |
From | Date | Subject | |
---|---|---|---|
Next Message | Mark Kirkwood | 2006-11-23 22:08:39 | Avg performance for int8/numeric |
Previous Message | Bruce Momjian | 2006-11-23 17:20:58 | Re: [PERFORM] Direct I/O issues |
From | Date | Subject | |
---|---|---|---|
Next Message | Brad Nicholson | 2006-11-23 20:40:15 | Re: Priority to a mission critical transaction |
Previous Message | Bruce Momjian | 2006-11-23 17:20:58 | Re: [PERFORM] Direct I/O issues |