Very much so. And even to make it a runtime-changeable pragma.
(Because, otherwise things like fink packages would have a difficult
decision to make. only the application really knows, whether syncing is
absolutely required, and to which degree. If the fink author needs to
make the choice,
On Feb 21, 2005, at 11:44 AM, Curtis King wrote:
On 21-Feb-05, at 11:11 AM, [EMAIL PROTECTED] wrote:
OK -- so, you are willing to accept the risk of non-recoverable
database corruption in the event of power outage or other kinds of
catastrophic system failure (including the plug being pulled on
On 21-Feb-05, at 11:11 AM, [EMAIL PROTECTED] wrote:
OK -- so, you are willing to accept the risk of non-recoverable
database corruption in the event of power outage or other kinds of
catastrophic system failure (including the plug being pulled on a
FireWire drive without it being properly
On 21-Feb-05, at 10:39 AM, [EMAIL PROTECTED] wrote:
It is a trade off between guaranteed data integrity and performance.
If there happen to be a bunch of other apps writing to the disk when
you do a SQLite transaction, then all of that data has to be flushed
to the disk. As Domnic said,
On Feb 21, 2005, at 9:54 AM, James Berry wrote:
On Feb 21, 2005, at 9:40 AM, Curtis King wrote:
I noticed this as well, so I profiled my call and found sync was
taking forever. I removed the following fcntl call, rc = fcntl(fd,
F_FULLFSYNC, 0);. Performance was back to normal.
Here are some
On Feb 21, 2005, at 9:40 AM, Curtis King wrote:
I noticed this as well, so I profiled my call and found sync was
taking forever. I removed the following fcntl call, rc = fcntl(fd,
F_FULLFSYNC, 0);. Performance was back to normal.
Here are some comments about F_FULLFSYNC, off the darwin list just
I noticed this as well, so I profiled my call and found sync was taking
forever. I removed the following fcntl call, rc = fcntl(fd,
F_FULLFSYNC, 0);. Performance was back to normal.
ck
7 matches
Mail list logo
