From: | Claudio Freire <klaussfreire(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Greg Stark <stark(at)mit(dot)edu>, Craig Ringer <craig(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Can we trust fsync? |
Date: | 2013-11-22 16:32:07 |
Message-ID: | CAGTBQpaU6ByOzrQTLBvD5mYq8RQm94RSic7Af794Djghg2tbYQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Nov 22, 2013 at 1:16 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> The original mail was referencing a problem with syncing *meta* data
>> though. The semantics around meta data syncs are much less clearly
>> specified, in part because file systems traditionally made nearly all meta
>> data operations synchronous. Doing plug-pull testing on Postgres would not
>> test meta data syncing very well since Postgres specifically avoids doing
>> much meta data operations by overwriting existing files and blocks as much
>> as possible.
>
> True. You're better off with a specialized testing program. (Though
> now you mention it, I wonder whether that program was stressing metadata
> or not.)
You can always stress metadata by leaving atime updates in their full
setting (whatever it is for that filesystem).
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2013-11-22 17:17:41 | Re: Suggestion: Issue warning when calling SET TRANSACTION outside transaction block |
Previous Message | Tom Lane | 2013-11-22 16:27:45 | Re: Building on S390 |