> Dmitry Yemanov [2011-10-25 17:55] :
>> 25.10.2011 14:39, Philippe Makowski wrote:
>>
>>> in fact with theses settings, FW=OFF is safer than before
>>> safe enough to be the default ?
>>
>> Even in the "paranoid mode" (MaxUnflushedWrites = 1) they still don't
>> guarantee the write order. So, if the crash happens while the
>> transaction is being committed, the database may get corrupted.
> hum
> would it be hard to have it in the good order
> or to have something like in PG
> http://www.postgresql.org/docs/9.1/static/wal-async-commit.html
> (I know we don't have WAL)
Shared cache opens some "new" possibilities for us. With it we can group
some expensive operations of few attachments into one less expensive.
I speak about group commit mostly but there are more operations which could
be grouped.
Regards,
Vlad
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
