| From: | "Jeffrey D(dot) Brower" <jeff(at)pointhere(dot)net> |
|---|---|
| To: | "Andreas Kostyrka" <andreas(at)mtg(dot)co(dot)at> |
| Cc: | "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, <pgsql-performance(at)postgresql(dot)org>, "Shankar K" <shan0075(at)yahoo(dot)com>, "eric soroos" <eric-psql(at)soroos(dot)net> |
| Subject: | Re: ext3 filesystem / linux 7.3 |
| Date: | 2003-04-02 17:07:57 |
| Message-ID: | 0a6f01c2f93a$6907bf50$0b02a8c0@pointhere.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
>> This would indicate that the PG transactioning is complimentary to the
filesystem journaling, not duplication.
>It's both. See the -o data=journal|data=ordered|data=writeback mount
>time option.
I did a RTFM on that but I am now confused again.
I am wondering what the *best* setting is with ext3. When I RTFM the man
page for mount, the data=writeback option says plainly that it is fastest
but in a crash old data is quite possibly on the dataset. The safest
*looks* to be data=journal since the journaling happens before writes are
committed to the file (and presumably the journal is used to update the file
on the disk to apply the journal entry to the disk file?) and the default is
data=ordered which says write to the disk AND THEN to the journal (which
seems bizarre to me).
How all of that works WITH and/or AGAINST PostgreSQL and what metadata
REALLY means is my bottom line quandary. Obviously that is where finding
the warm and fuzzy place between speed and safety is found.
Jeff
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2003-04-02 20:05:30 | Re: ext3 filesystem / linux 7.3 |
| Previous Message | Andreas Pflug | 2003-04-02 16:45:46 | Re: ext3 filesystem / linux 7.3 |