From: | Pierre-Frédéric Caillaud <lists(at)boutiquenumerique(dot)com> |
---|---|
To: | pgsql-performance(at)postgresql(dot)org |
Subject: | Reiser4 |
Date: | 2004-08-13 16:12:34 |
Message-ID: | opscohy8dvcq72hf@musicbox |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-performance |
ReiserFS 4 is (will be) a filesystem that implements transactions.
Are there any plans in a future Postgresql version to support a special
fsync method for Reiser4 which will use the filesystem's transaction
engine, instead of an old kludge like fsync(), with a possibility of
vastly enhanced performance ?
Is there also a possibility to tell Postgres : "I don't care if I lose 30
seconds of transactions on this table if the power goes out, I just want
to be sure it's still ACID et al. compliant but you can fsync less often
and thus be faster" (with a possibility of setting that on a per-table
basis) ?
Thanks.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-08-13 16:18:50 | Re: Trigger function returning null |
Previous Message | Thomas Hallgren | 2004-08-13 16:08:53 | Re: Trigger function returning null |
From | Date | Subject | |
---|---|---|---|
Next Message | Matt Clark | 2004-08-13 16:17:10 | Re: insert |
Previous Message | Pierre-Frédéric Caillaud | 2004-08-13 16:06:59 | Re: fsync vs open_sync |