| From: | "Zeugswetter Andreas DAZ SD" <ZeugswetterA(at)spardat(dot)at> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | "Simon Riggs" <simon(at)2ndquadrant(dot)com>, "Greg Stark" <gsstark(at)mit(dot)edu>, "Russell Smith" <mr-russ(at)pws(dot)com(dot)au>, <josh(at)agliodbs(dot)com>, "Postgres Hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Checkpoint cost, looks like it is WAL/CRC |
| Date: | 2005-07-08 07:34:16 |
| Message-ID: | E1539E0ED7043848906A8FF995BDA57945BAFB@m0143.s-mxs.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>>> The point here is that fsync-off is only realistic for development
or
>>> playpen installations. You don't turn it off in a production
>>> machine, and I can't see that you'd turn off the full-page-write
>>> option either. So we have not solved anyone's performance problem.
>
>> Yes, this is basically another fsync-like option that isn't for
>> production usage in most cases. Sad but true.
>
> Just to make my position perfectly clear: I don't want to see
> this option shipped in 8.1.
Why not ? If your filesystem buffer size matches your pg page size,
and you have a persistent write cache, the option makes perfect sense.
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2005-07-08 09:17:51 | Re: Checkpoint cost, looks like it is WAL/CRC |
| Previous Message | Neil Conway | 2005-07-08 06:30:39 | Re: User's exception plpgsql |