Re: [sqlite] Problems after upgrade

[Holger Eitzenberger]

[EMAIL PROTECTED] writes:

>> Profiling revealed that version 3.4.2 seems to have some kind of problem
>> with the DB if created with version 3.3.8 of the library.  These are the
>> first lines of the profiled data on an (despite sqlite) basically idle
>> system:
>> 
>>  samples  %app name symbol name
>>  574   7.1616  libsqlite3.so.0.8.6  sqlite3VdbeExec
>>  485   6.0512  libsqlite3.so.0.8.6  __i686.get_pc_thunk.bx
>>  315   3.9301  libsqlite3.so.0.8.6  sqlite3VdbeSerialType
>>  265   3.3063  libsqlite3.so.0.8.6  sqlite3VdbeSerialPut

> The database file format has not changed.  You are the first
> person to report any similar problems.  Are you *certain* that
> is the database upgrade that is causing your problem?

Well, after profiling I stopped my application, moved the DB away and
restarted.  Then the problem went away.

Also, after upgrading Sqlite my application was restarted, so I do not
any reason to fail.  Hmm...

Sqlite 3.3.8 was the version as it is available on SuSE SLES10, while the
updated version is the unpatched 3.4.2.  Maybe I should go check the
SuSE patches...

  /holger

-
To unsubscribe, send email to [EMAIL PROTECTED]
-

[sqlite] Problems after upgrade

[Holger Eitzenberger]

Hi,

I was using Sqlite library 3.3.8 before upgrading it to version 3.4.2 on
Linux.

Right after upgrade I noticed that the CPU load of my application, which
is shared linked to the library, increased considerably.

Profiling revealed that version 3.4.2 seems to have some kind of problem
with the DB if created with version 3.3.8 of the library.  These are the
first lines of the profiled data on an (despite sqlite) basically idle
system:

 samples  %app name symbol name
 574   7.1616  libsqlite3.so.0.8.6  sqlite3VdbeExec
 485   6.0512  libsqlite3.so.0.8.6  __i686.get_pc_thunk.bx
 315   3.9301  libsqlite3.so.0.8.6  sqlite3VdbeSerialType
 265   3.3063  libsqlite3.so.0.8.6  sqlite3VdbeSerialPut
 263   3.2813  libsqlite3.so.0.8.6  sqlite3PutVarint
 228   2.8447  audld.plx(no symbols)
 227   2.8322  libc-2.4.so  _int_malloc
 212   2.6450  libfreetype.so.6.3.8 (no symbols)
 200   2.4953  vmlinux-2.6.16.43-54-default default_idle
 182   2.2707  libcsscan.so convert_line
 160   1.9963  libsqlite3.so.0.8.6  sqlite3PagerAcquire
 149   1.8590  confd.plx(no symbols)
 ...

Now, despite removing the old lib, is there some chance to keep the old
DB and kind of "repair" it?

Also, is there some kind of policy which tells me if the format of
the DB changed?

Thanks.

  /holger



-
To unsubscribe, send email to [EMAIL PROTECTED]
-