On Wednesday 26 October 2005 18:12, Russell Howe wrote:
> Paul Heinlein wrote:
> > At the risk of being somewhat off-topic, I'll add that the same is true
> > of SQLite. In SQLite 2.8, setting the default_synchronous flag to OFF
> > will speed things up markedly:
> >
> > echo 'PRAGMA default_synchronous=0;' | sqlite bacula.db
>
> I posted about this previously:
>
> http://article.gmane.org/gmane.comp.bacula.user/16853/match=pragma
>
> Looks like they just removed the option to default all databases to
> non-synchronous operation in SQLite 3.0, requiring you to manually set
> your databases to be asynchronous. A good decision, I would say.
>
> I think the 'default_synchronous' setting will only apply to databases
> when they're created (or, to put it another way, changing it will not
> affect any existing databases).
>
> Since you're taking backups of the database, and you can restore the
> catalog by using bscan, I don't see the need for synchronous operation,
> unless you absolutely cannot have your database server down for the time
> it would take to restore the catalog in the event of a power failure or
> somesuch.
>
> I'll be turning it off tonight, to see what difference it makes to
> performance...
The default for Bacula 1.37 SQLite is:
PRAGMA default_synchronous = OFF;
which I implemented shortly after Russell's original post. Thanks Russell.
--
Best regards,
Kern
(">
/\
V_V
-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
