[pkg-bacula-devel] Bug#854684: bacula doesn't officially support SQLite3

Carsten Leonhardt leo at debian.org
Fri Feb 10 00:00:01 UTC 2017

Sven Hartge <sven at svenhartge.de> writes:

> I was quite surprised to see sqlite3 being the default. I would have sworn 
> the default being MySQL.

I didn't change it because I wasn't aware that it's not really supported.

> But at least the description for bacula-director-sqlite3 mentions sqlitt3 
> being only useful for small or test installations. (Maybe we can put in a 
> warning via NEWS for Buster [too late for Stretch for that] that SQLite3 
> is unsupported and should no longer be used.)

I'll put it on the TODO list for consideration, we have some time to
think about it until the stretch release...

> Concerning the default database: I think upstream favors PostgreSQL.

So do I, although I used SQLite3 on my first installation and never had
problems (except when the database finally grew too big).

I liked it as a default because it's uncomplicated. But yes, it's
probably best to follow upstream's recommendation in this case.

 - Carsten

More information about the pkg-bacula-devel mailing list