[Python-Dev] Re: RELEASED Python 2.3.1 (original) (raw)
Jeremy Hylton jeremy at zope.com
Sat Sep 27 13:28:39 EDT 2003
- Previous message: [Python-Dev] Re: RELEASED Python 2.3.1
- Next message: [Python-Dev] Re: RELEASED Python 2.3.1
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Sat, 2003-09-27 at 06:30, Martin v. Löwis wrote:
"Jason R. Mastaler" <jason at mastaler.com> writes:
> > I don't think the problem is severe; os.fsync is rarely used. > > How did you arrive at this notion? >From four considerations: 1. It did not show up in any of the tests. 2. To use it, you have to use "bare" file descriptors; this is relatively un-pythonic. 3. To use it, you have to worry about data getting on the disk - this really requires some kind of expert application. 4. It is not universally available, so the expert application I had to assume in 3) would most likely test for presence of fsync, and fall back to just not use it (and perhaps invoke sync(1) instead).
I suppose ZODB is such an expert application. It has to cope with systems that do not provide fsync(), but it provides degraded service on such platforms. It is very important for the database to call fsync() when it commits a transaction.
Jeremy
- Previous message: [Python-Dev] Re: RELEASED Python 2.3.1
- Next message: [Python-Dev] Re: RELEASED Python 2.3.1
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]