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

Re: svn commit: r1865522 - /subversion/trunk/subversion/libsvn_subr/sqlite3wrapper.c

From: Daniel Shahaf <d.s_at_daniel.shahaf.name>
Date: Tue, 20 Aug 2019 18:05:45 +0000

kotkov_at_apache.org wrote on Tue, 20 Aug 2019 09:18 +00:00:
> When compiling SQLite, set the SQLITE_DEFAULT_MEMSTATUS=0 compile-time option.
> This is the recommended option that is not enabled by default. Setting it to
> zero avoids using a mutex (and thus suffering a performance penalty) during
> every sqlite3_malloc() call, where this mutex is used to properly update the
> allocations stats. We don't use sqlite3_status(), so set this option to zero.
> See https://sqlite.org/compile.html#recommended_compile_time_options

Would it break anything if some application that uses libsvn had
its own copy of SQLite that was compiled with another SQLITE_DEFAULT_MEMSTATUS
value? I don't see anything about that in the linked page.


Received on 2019-08-20 20:05:51 CEST

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