On Sun, Dec 12, 2010 at 7:33 PM, Robert Haas <robertmh...@gmail.com> wrote: > On Sun, Dec 12, 2010 at 9:31 PM, Rob Wultsch <wult...@gmail.com> wrote: >> On Fri, Dec 10, 2010 at 5:34 PM, Cédric Villemain >> <cedric.villemain.deb...@gmail.com> wrote: >>> 2010/12/8 Kineticode Billing <da...@kineticode.com>: >>>> On Dec 8, 2010, at 10:37 AM, Chris Browne wrote: >>>> >>>>> Other possibilities include TRANSIENT, EPHEMERAL, TRANSIENT, TENUOUS. >>>> >>>> EVANESCENT. >>> >>> UNSAFE ? >>> >> <troll> >> MyISAM >> </troll> > > Heh. But that would be corrupt-on-crash, not truncate-on-crash, no? > > -- > Robert Haas > EnterpriseDB: http://www.enterprisedb.com > The Enterprise PostgreSQL Company > <troll> Yep. Truncate-on-shutdown MySQL options are the MEMORY and PBXT (using the memory resident option). </troll>
I like TRANSIENT but wonder if MEMORY might be more easily understood by users. -- Rob Wultsch wult...@gmail.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
