Re: unlogged tables

From: Rob Wultsch <wultsch(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Cédric Villemain <cedric(dot)villemain(dot)debian(at)gmail(dot)com>, Kineticode Billing <david(at)kineticode(dot)com>, Chris Browne <cbbrowne(at)acm(dot)org>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: unlogged tables
Date: 2010-12-13 06:15:34
Message-ID: AANLkTi=C3X5jwb2mR3h2mHZ63S-M00oVqf5BpA0pCfCr@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Dec 12, 2010 at 7:33 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Sun, Dec 12, 2010 at 9:31 PM, Rob Wultsch <wultsch(at)gmail(dot)com> wrote:
>> On Fri, Dec 10, 2010 at 5:34 PM, Cédric Villemain
>> <cedric(dot)villemain(dot)debian(at)gmail(dot)com> wrote:
>>> 2010/12/8 Kineticode Billing <david(at)kineticode(dot)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
wultsch(at)gmail(dot)com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Itagaki Takahiro 2010-12-13 06:31:42 Re: SQL/MED - file_fdw
Previous Message Rob Wultsch 2010-12-13 05:59:39 Re: ALTER TABLE ... ADD FOREIGN KEY ... NOT ENFORCED