On Wed, Feb 9, 2011 at 23:06, Stefan Sperling <stsp_at_elego.de> wrote:
> On Wed, Feb 09, 2011 at 10:56:35PM +0300, Ivan Zhakov wrote:
>> On Wed, Feb 9, 2011 at 17:40, Ivan Zhakov <ivan_at_visualsvn.com> wrote:
>> > On Windows there is FILE_ATTRIBUTE_TEMPORARY  attribute, which
>> > prevents file to be written to disk:
>> > [[[
>> > Specifying the FILE_ATTRIBUTE_TEMPORARY attribute causes file systems
>> > to avoid writing data back to mass storage if sufficient cache memory
>> > is available, because an application deletes a temporary file after a
>> > handle is closed. In that case, the system can entirely avoid writing
>> > the data. Although it does not directly control data caching in the
>> > same way as the previously mentioned flags, the
>> > FILE_ATTRIBUTE_TEMPORARY attribute does tell the system to hold as
>> > much as possible in the system cache without writing and therefore may
>> > be of concern for certain applications.
>> > ]]]
>> > May be we should submit a patch to SQLite to use this attribute?
>> >  http://msdn.microsoft.com/en-us/library/aa363858%28v=vs.85%29.aspx
>> Well, I've checked SQLite source code and it seems SQLite uses
>> FILE_ATTRIBUTE_TEMPORARY attribute when creating temporary database,
>> database journal and other temporary files. So temporary tables backed
>> up by file should be serious problem in theory.
> Did you mean to say that it should *not* be a serious problem?
Oops, sorry for typo. Yes, I mean that temporary tables backed up by
file should *NOT* be serious problem in theory.
Received on 2011-02-09 21:15:42 CET