Does it make sense to talk about concurrency when it is accessed by the only process (bareos on our case) ?
On Friday, November 7, 2014 5:28:47 PM UTC+3, [email protected] wrote: > Zitat von Stanislav German-Evtushenko <[email protected]>: > > > On Friday, November 7, 2014 5:17:54 PM UTC+3, Hunt, Phillip wrote: > >> Yes, sqlite is NOT a good database. Bareos writes millions of file > >> records to the file. Sqlite will run out of pointers and > >> performance will greatly suffer very quickly. > >> > >> Sqlite is a FLAT file database, not an indexed one. It simulates a > >> database so a developer does not have to figure out SQL/db setup > >> stuff while developing. > > > > So the only concern is performance. Am I right? > > To some degree yes. SQlite is a file base database which is basically > a key/value store. The more complex dependencies with > columns/rows/tables are managed in the library which is used inside > the client code. This lead to problems with concurrency and > performance if you have somewhat complex queries or schemas. If you > have a small backup set which is never intended to grow you can use > SQlite, but if you intend to use Bareos as a central network backup i > would recommend using PostgreSQL which doesn't need any attention and > is better suited for the task. > > Regards > > Andreas -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
