If you need to run some database really fast, try to put only all your
indexes onto ram disk. Look here... http://www.linux.com/feature/142658
They use SSD to store indexes (not data) for postgresql. A think the
same conclusions should apply for ram disk too.
And in wrost case (power off for RAM disk or wear out for SSD) you need
only a reindex to build your indexes again
Scott Marlowe napsal(a):
On Mon, Apr 13, 2009 at 2:06 PM, aravind chandu <avin_friends@xxxxxxxxx> wrote:
Hello,
Thanks for your reply,but what I am actually looking for is
database should be an in-memory database and at the same i want to store
that data into disk so that data won't be lost when the system restarts or
in case of power failure. Can you guys tell me the procedure how to do this?
your help will he greatly appreciated.
But that's just the point people have been making. A small enough db
will be cached completely in memory, and the only time you'll have to
access the disks is the first read, and during writes, which can be
made to happen mostly after the fact and not influence the rest of the
db.
You're trying to reinvent a wheel to solve a non-existent problem.
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
