[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Subversion 1.9 working copy compatibility

From: Branko Čibej <brane_at_wandisco.com>
Date: Mon, 16 Mar 2015 20:28:09 +0100

On 16.03.2015 17:49, Bert Huijben wrote:
>
>> -----Original Message-----
>> From: Marc Strapetz [mailto:marc.strapetz_at_syntevo.com]
>> Sent: maandag 16 maart 2015 17:14
>> To: users_at_subversion.apache.org
>> Subject: Re: Subversion 1.9 working copy compatibility
>>
>> On 16.03.2015 16:34, Branko Čibej wrote:> On 16.03.2015 15:58, Marc
>> Strapetz wrote:
>>>> From my experiments with Subversion 1.9 binaries and the listed
>>>> changes in the release notes, Subversion 1.9 seems to be backwards
>>>> compatible with Subversion 1.8 working copies. Is that correct?
>>> There are no schema changes, but 1.9 is faster at many working copy
>>> operations due to more optimized queries.
>> Does that mean than an "svn upgrade" should still be invoked to get
>> these optimized queries?
> As 1.9 is not final yet we can't definitely answer that. (We might still need a format bump, etc. ... although we will try to avoid that)
>
> Currently it looks like you don't need to call svn upgrade.
>
> And it looks like both 1.9 and a future 1.8 will improve performance on working copies initially created/upgraded with 1.8.0-1.8.7, but not already explicit 'svn upgrade'-d with a later version, when it internally uses Sqlite 3.8 or later.
>
> The performance fix is nominated for both 1.9 and 1.8. For 1.9 it is accepted for backport, but for 1.8 it misses a final vote.

Just to clarify, since Marc actually knows something about one of the
performance issues: in 1.9 and trunk (and the proposed 1.8 backport),
we'll now create the SQLite stats table (that improves the query
optimizer results) when the WC database is opened, if the table doesn't
already exist. Since 1.8.8 (?) you can call "svn upgrade" to add that table.

-- Brane
Received on 2015-03-16 20:28:43 CET

This is an archived mail posted to the Subversion Users mailing list.