On 16.10.2015 13:14, Philip Martin wrote:
> Philip Martin <philip.martin_at_wandisco.com> writes:
>
>> "Bert Huijben" <bert_at_qqmail.nl> writes:
>>
>>> I'm not able to answer all that, but I do know that your change will
>>> slow Subversion down on Samba shares as used from Windows systems with
>>> that flag. And once one user used it in that way it will stay slow
>>> because the journal mode is stored in the database.
>>>
>>> I don't think just touching a working copy with a client should ever
>>> have such an effect on a working copy.
>> The journal mode is set to TRUNCATE every time we open the database,
>> that doesn't change with my patch. Are you saying that TRUNCATE will be
>> ignored after some previous connection uses DELETE?
> The documentation explicitly states that journal_mode=WAL stays in
> effect for later connections, but doesn't say the same for the other
> modes:
I think that means "for later concurrent connections to the database",
meaning until the last process closes it. That would make sense, because
you can't combine WAL mode with either truncate or delete at the same time.
-- Brane
Received on 2015-10-16 19:18:47 CEST