Search Postgresql Archives

Re: [pgsql-general] In memory tables/databases

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



"Alexander Todorov" <alexx.todorov@xxxxxxxxx> writes:
> On 7/2/07, Tom Lane <tgl@xxxxxxxxxxxxx> wrote:
>> 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.

You might as well start with a freshly initdb'd cluster (all on ramdisk)
and do pg_restore from a full dump instead of a data-only dump.  The
former will probably be faster as well as more foolproof.

			regards, tom lane


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux