From: | Maarten Boekhold <boekhold(at)tibco(dot)com> |
---|---|
To: | Brian E Gallew <geek+(at)cmu(dot)edu> |
Cc: | hackers <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Re: [HACKERS] Fwd: Joins and links |
Date: | 1999-07-12 13:34:39 |
Message-ID: | 3789EEEF.A5B584F6@tibco.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> > > Well, I personally dont even know, how I could keep my entire PostgreSQL
> > > DB in RAM :)
> >
> > I thought about doing this once on a Linux box. What I was thinking about was
> > creating a large RAM disk, and use that disk together with a physical drive in
> > a mirror setup. However, I was never able to create a large enough RAM disk back then
[...]
> Maarten, PostgreSQL keeps it's data in the filesystem, rather than on
> raw disks. Due to the nature of *nix, all you need to do to keep your
> entire DB in memory is have enough memory. The buffer cache will do
> the rest, for you. Of course, you still need to start it up with -F
I know, but there's no *guarantee* that the complete database is going to be in RAM.
That's what I was trying to solve. Putting the thing on a RAM disk would guarantee that
it is.
Maarten
--
Maarten Boekhold, boekhold(at)tibco(dot)com
TIBCO Finance Technology Inc.
The Atrium
Strawinskylaan 3051
1077 ZX Amsterdam, The Netherlands
tel: +31 20 3012158, fax: +31 20 3012358
http://www.tibco.com
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 1999-07-12 13:34:55 | Re: [HACKERS] Hashing passwords (was Updated TODO list) |
Previous Message | Gene Sokolov | 1999-07-12 13:32:46 | Re: [HACKERS] Re: Hashing passwords (was Updated TODO list) |