From: | Doug McNaught <doug(at)mcnaught(dot)org> |
---|---|
To: | Shane Wright <shane(dot)wright(at)edigitalresearch(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: mount -o async - is it safe? |
Date: | 2006-01-19 14:34:00 |
Message-ID: | 87k6cwthgn.fsf@asmodeus.mcnaught.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Shane Wright <shane(dot)wright(at)edigitalresearch(dot)com> writes:
> Actually I thought that *all* the database had to have fsync() work correctly;
> not for integrity on failed transactions, but to maintain integrity during
> checkpointing as well. But I could well be wrong!
I think you're write, but what I was thinking of is the scenario where
WAL writes are done in small increments, then committed with fsync()
once a full page has been written. With a sync mount this would
result in the equivalent of fsync() for every small write, which would
hurt a lot.
I dimly recall this sort of thing being discussed in the past, but I
don't know offhand whether PG does its WAL writes in small chunks or
page-at-a-time.
-Doug
From | Date | Subject | |
---|---|---|---|
Next Message | Stephan Szabo | 2006-01-19 14:52:47 | Re: PostgreSQL Top 10 Wishlist |
Previous Message | Ian Harding | 2006-01-19 14:31:28 | Re: tsearch2 and "how to use" |