Re: [HACKERS] TODO item

From: Don Baccus <dhogaza(at)pacifier(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>, Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>, pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] TODO item
Date: 2000-02-08 05:03:51
Message-ID: 3.0.1.32.20000207210351.010b11a0@mail.pacifier.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

At 10:26 PM 2/7/00 -0500, Tom Lane wrote:
>Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
>> Seems like little redesign needed, except for adding the need_fsync
>> flag. Should be no more than about 20 lines.
>
>If you think this is a twenty line fix, take a deep breath and back
>away slowly. You have not understood the problem.

And, again, thank you.

>This is not a trivial change.

I was actually through that code months ago, wondering why (ahem)
PG was so stupid about disk I/O and reached the same conclusion.

Therefore, I was more than pleased when a simple fix to get rid
of fsync's on read-only transactions arose. In my application
space, this alone gave a huge performance boost.

WAL...that's it. If Vadim is going to be unavailable because
of his new job, we'll need to figure out another way to do it.

- Don Baccus, Portland OR <dhogaza(at)pacifier(dot)com>
Nature photos, on-line guides, Pacific Northwest
Rare Bird Alert Service and other goodies at
http://donb.photo.net.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Chris Bitmead 2000-02-08 05:56:06 Bug in cursors??
Previous Message Chris Bitmead 2000-02-08 05:03:38 Regression tests...