title: Database design for heavy timed data logging
body: <p>I have an application where I receive each data 40.000 rows. I have 5 million rows to handle (500 Mb MySQL 5.0 database).</p>
  
  <p>Actually, those rows are stored in the same table => slow to update, hard to backup, etc.</p>
  
  <p>Which kind of scheme is used in such application to allow long term accessibility to the data without problems with too big tables, easy backup, fast read/write ?</p>
  
  <p>Is <code>postgresql</code> better than <code>mysql</code> for such purpose ?</p>