From: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | "Ron Johnson" <ron(dot)l(dot)johnson(at)cox(dot)net> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: DB on a ramdisk (was Re: Temporary, In-memory Postgres DB?) |
Date: | 2007-11-07 17:00:18 |
Message-ID: | dcc563d10711070900j299c0298g72e0b2092dc64520@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 11/7/07, Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 11/07/07 09:58, Tom Lane wrote:
> > Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net> writes:
> >> On 11/07/07 09:03, Gauthier, Dave wrote:
> >>> Is there such a thing as a temporary, probably in-memory, version of a
> >>> Postgres DB?
> >
> >> If you have enough RAM, and your database is small enough, the OS
> >> will eventually cache the whole thing.
> >
> > Or put it on a ramdisk filesystem.
>
> But doesn't that just add more overhead and reduce the amount of
> memory that the OS can cache things in?
Didn't say it was the smart thing to do. Just that you could do it.
I think if one is looking at in memory databases, PostgreSQL is NOT
the first choice really.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-11-07 17:04:36 | Re: DB on a ramdisk (was Re: Temporary, In-memory Postgres DB?) |
Previous Message | rihad | 2007-11-07 16:57:59 | Re: prepared statements suboptimal? |