From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Pierre-Frédéric Caillaud <lists(at)boutiquenumerique(dot)com> |
Cc: | pgsql-performance(at)postgresql(dot)org, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [PERFORM] Reiser4 |
Date: | 2004-08-14 01:30:47 |
Message-ID: | 200408140130.i7E1Ulf06800@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-performance |
Pierre-Frdric Caillaud wrote:
> 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) ?
I have been thinking about this. Informix calls it buffered logging and
it would be a good feature.
Added to TODO:
* Allow buffered WAL writes and fsync
Instead of guaranteeing recovery of all committed transactions, this
would provide improved performance by delaying WAL writes and fsync
so an abrupt operating system restart might lose a few seconds of
committed transactions but still be consistent. We could perhaps
remove the 'fsync' parameter (which results in an an inconsistent
database) in favor of this capability.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2004-08-14 01:31:42 | Re: Reiser4 |
Previous Message | Robert Treat | 2004-08-14 01:18:10 | Re: Calling PL functions with named parameters |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2004-08-14 01:31:42 | Re: Reiser4 |
Previous Message | Chris Cheston | 2004-08-14 01:27:04 | Replication: Slony-I vs. Mammoth Replicator vs. ? |