| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | David Fetter <david(at)fetter(dot)org> |
| Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Alexander Todorov <alexx(dot)todorov(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: [pgsql-general] In memory tables/databases |
| Date: | 2007-07-01 23:04:11 |
| Message-ID: | 18394.1183331051@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
David Fetter <david(at)fetter(dot)org> writes:
> On Sun, Jul 01, 2007 at 03:55:11PM -0400, Alvaro Herrera wrote:
>> So mount a ramdisk and initdb in there.
> You could also put a tablespace on a ramdisk and create the table
> there.
The fresh-initdb approach is more likely to work without any strange
corner cases. If you try a setup where the system catalogs are on
persistent storage but you have a tablespace on ramdisk, then after
restart you'll have pg_class entries referencing files that don't exist
anymore, which I believe will provoke errors.
Also, I doubt the OP wants his WAL on real storage either ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2007-07-01 23:04:17 | Re: [pgsql-general] In memory tables/databases |
| Previous Message | Bjorn Boulder | 2007-07-01 22:57:43 | [pgsql.general] Problem connecting PostgreSQL 8.2 to Rails 1.2 |