Re: [pgsql-general] In memory tables/databases
От | Alexander Todorov |
---|---|
Тема | Re: [pgsql-general] In memory tables/databases |
Дата | |
Msg-id | 6e97ff300707011614p72f7d779g31abb6171fa6b902@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [pgsql-general] In memory tables/databases (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: [pgsql-general] In memory tables/databases
|
Список | pgsql-general |
On 7/2/07, Tom Lane <tgl@sss.pgh.pa.us> wrote: > David Fetter <david@fetter.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. Thanks for this hint. That looks like what I was looking for. > > 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. I believe error will occur if trying to access these objects. To avoid this pg_dump/pg_restore may be useful and recreating the tables/indexes after restart. This will emulate the MySQL behaviour where tables definitions is kept on disk and contents kept in memory.
В списке pgsql-general по дате отправления: