| From: | Michael Stone <mstone+postgres(at)mathom(dot)us> |
|---|---|
| To: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
| Cc: | mark(at)mark(dot)mielke(dot)cc, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Postgresql Performance on an HP DL385 and |
| Date: | 2006-08-15 20:53:03 |
| Message-ID: | 20060815205300.GX2900@mathom.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Tue, Aug 15, 2006 at 02:15:05PM -0500, Jim C. Nasby wrote:
>Now, if
>fsync'ing a file also ensures that all the metadata is written, then
>we're probably fine...
...and it does. Unclean shutdowns cause problems in general because
filesystems operate asynchronously. postgres (and other similar
programs) go to great lengths to make sure that critical operations are
performed synchronously. If the program *doesn't* do that, metadata
journaling isn't a magic wand which will guarantee data integrity--it
won't. If the program *does* do that, all the metadata journaling adds
is the ability to skip fsck and start up faster.
Mike Stone
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Stone | 2006-08-15 20:58:59 | Re: Postgresql Performance on an HP DL385 and |
| Previous Message | Vivek Khera | 2006-08-15 20:41:55 | Re: Dell PowerEdge 2950 performance |