On Wed, Mar 30, 2005 at 08:41:43PM -0600, John Arbash Meinel wrote:
> If all you are doing is append only logging, the fastest thing is
> probably just a flat file. You could have something that comes along
> later to move it into the database. It doesn't really sound like you are
> using any featu
The reason: if the power cord is yanked, the OS _must_ boot back up in
good condition. If the DB is corrupted, whatever, nuke it then re-
initialize it. But the OS must survive act-of-god events.
Well, in that case :
- Use reiserfs3 for your disks
- Use MySQL with MyISAM tables
Florin Andrei wrote:
On Wed, 2005-03-30 at 20:11 -0600, John Arbash Meinel wrote:
Florin Andrei wrote:
For performance reasons, i was thinking to keep the tables append-only,
and simply rotate them out every so often (daily?) and delete those
tables that are too old. Is that a good idea?
If you
Florin Andrei wrote:
On Wed, 2005-03-30 at 19:59 -0600, John Arbash Meinel wrote:
Put pg_xlog onto the same drive as the OS, not the drive with the database.
I forgot to mention: the OS drive is purposefully made very slow - the
write cache is turned off and the FS is Ext3 with data=journal. Is t
On Wed, 2005-03-30 at 20:11 -0600, John Arbash Meinel wrote:
> Florin Andrei wrote:
> >
> >For performance reasons, i was thinking to keep the tables append-only,
> >and simply rotate them out every so often (daily?) and delete those
> >tables that are too old. Is that a good idea?
> >
> If you are
On Wed, 2005-03-30 at 19:59 -0600, John Arbash Meinel wrote:
> Put pg_xlog onto the same drive as the OS, not the drive with the database.
I forgot to mention: the OS drive is purposefully made very slow - the
write cache is turned off and the FS is Ext3 with data=journal. Is then
still ok to put
Florin Andrei wrote:
On Wed, 2005-03-30 at 17:50 -0800, Florin Andrei wrote:
Function: Essentially a logging server. There are two applications (like
syslog) on the same box that are logging to pgsql, each one to its own
database. There are a few tables in one DB, and exactly one table in the
othe
On Wed, 2005-03-30 at 17:50 -0800, Florin Andrei wrote:
> Function: Essentially a logging server. There are two applications (like
> syslog) on the same box that are logging to pgsql, each one to its own
> database. There are a few tables in one DB, and exactly one table in the
> other.
> Most of
Florin Andrei wrote:
Hardware: relatively modern Intel CPU, OS and database each on its own
IDE hard-drive (separate IDE cables). Enough memory, i think, but i
can't add too much (not beyond 1GB).
Software: Linux-2.6, pgsql-8.0.1
Function: Essentially a logging server. There are two applications (l