Author Topic: mySQL vs PostgreSQL vs sqlite  (Read 7113 times)

Offline cbrace

  • Full Member
  • ***
  • Posts: 75
mySQL vs PostgreSQL vs sqlite
« on: March 24, 2008, 09:15:46 AM »
Hi all,

I am in the process of installing roundceube on my FreeBSD 7 server. While I wait for a FreeBSD packaging issue to be sorted out, I have a rather general question:

Which database backend to use?

My initial inclination is to go with sqlite. My installation will basically be for use on my SoHo gateway/server; I am not sure I need all the firepower of a Postgres or mySQL. The server on which I will be running roundcube is an older Pentium IV with only 512 MB, and I hoping sqlite has a smaller memory footprint than the others. That being said, the message database could become fairly big (by way of example: after using gmail for about two years, my account has around 100k messages, using about 3GB, thanks to so busy mailling lists I subscribe to). If for some reason, I later want to migrate to Postgres, will be be possible to import the sqlite db?

Thanks.


 


Offline jimcavoli

  • Jr. Member
  • **
  • Posts: 37
Re: mySQL vs PostgreSQL vs sqlite
« Reply #1 on: March 27, 2008, 12:50:58 AM »
cbrace,
Moving from SQLite to Postgres won't be too big a deal, especially since tools like SQLiteAdmin (http://sqliteadmin.orbmu2k.de/) and pgAdmin (http://www.pgadmin.org/) can handle exports and imports in formats like CSV, though the pgAdmin import is a bit tricky. One thing to consider is that if you find your database getting uncontrollably large or that it eats too much processing power, it could easily be moved to a different computer, but you should be alright for a while on your P4.
I hope this helps you out.
 --Jim