Mailing-List: contact dev-help@subversion.apache.org; run by ezmlm
Precedence: bulk
From: Philip Martin <philip.martin@wandisco.com>
To: "Bert Huijben" <bert@qqmail.nl>
Cc: 'Branko =?utf-8?Q?=C4=8Cibej'?= <brane@apache.org>,
  <dev@subversion.apache.org>
Subject: Re: NFS performance regression in 1.9
References: <87vba82pgl.fsf@wandisco.com> <561FD7F4.3090604@apache.org>
	<87k2qo2fpy.fsf@wandisco.com>
	<0f7101d10776$412ba610$c382f230$@qqmail.nl>
Date: Thu, 15 Oct 2015 19:44:05 +0100
In-Reply-To: <0f7101d10776$412ba610$c382f230$@qqmail.nl> (Bert Huijben's
	message of "Thu, 15 Oct 2015 20:21:02 +0200")
Message-ID: <87fv1c2cqy.fsf@wandisco.com>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.4 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain

"Bert Huijben" <bert@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
doesn't appear to support you:

  https://sqlite.org/pragma.html#pragma_journal_mode

  This pragma queries or sets the journal mode for databases associated
  with the current database connection.

Ivan's original change r1659426 stated:

  The TRUNCATE and DELETE journal modes are compatible, so different
  Subversion clients with different journal mode should just work with same 
  working copy without problems.

-- 
Philip Martin
WANdisco