2009/4/13 aravind chandu <avin_friends@xxxxxxxxx>:
>
>
> Hello,
>
> Thanks for your reply,but what I am actually looking for is
> database should be an in-memory database and at the same i want to store
> that data into disk so that data won't be lost when the system restarts or
> in case of power failure. Can you guys tell me the procedure how to do this?
> your help will he greatly appreciated.
>
> Thanks,
> Avin.
>
Oh, well... there is a way but is not recomended.
So you can make the tables on memory and with a trigger update on disk...
you can call this inverted materialized views (because in general you
update the views on memory but not in the disk).
But there is a problem... if you update on memory and a shutdown
occurs and the trigger didn't start... you lost this record :( I must
say that you
That's because i prefer have a database in disk and have updatable
views in memory :)
--
Emanuel Calvo Franco
Sumate al ARPUG !
(www.postgres-arg.org -
www.arpug.com.ar)
ArPUG / AOSUG Member
Postgresql Support & Admin
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
