On Sun, Mar 16, 2008 at 1:02 PM, Karl Denninger <[EMAIL PROTECTED]> wrote:
>
> >
> The key issue on RAM is not whether the database will fit into RAM (for
> all but the most trivial applications, it will not)
I would argue that many applications where the data fits into memory
are not trivial.
Craig Ringer wrote:
Robert Powell wrote:
To whom it may concern,
I'm looking for a file server that will give me a high level of
redundancy and high performance for a postgres database.
For strong redundancy and availability you may need a secondary server
and some sort of replication set
Robert Powell wrote:
To whom it may concern,
I'm looking for a file server that will give me a high level of
redundancy and high performance for a postgres database.
For strong redundancy and availability you may need a secondary server
and some sort of replication setup (be it a WAL-follow
What's the expected transaction split (read/write)?
If mostly READs (e.g. SELECTs) then its very, very hard to do better
from a performance perspective than Raid 1 with the transaction log on a
separate array (physically separate spindles)
I run a VERY busy web forum on a Quadcore Intel box w
To whom it may concern,
I'm looking for a file server that will give me a high level of
redundancy and high performance for a postgres database. The server
will be running only postgres as a backend service, connected to a front
end server with the application on it.
I was thinking along th
