Re: Unlogged vs. In-Memory

From: "Jehan-Guillaume (ioguix) de Rorthais" <ioguix(at)free(dot)fr>
To: Rob Wultsch <wultsch(at)gmail(dot)com>
Cc: damien clochard <damien(at)dalibo(dot)info>, Roy Hann <specially(at)processed(dot)almost(dot)meat>, pgsql-advocacy(at)postgresql(dot)org
Subject: Re: Unlogged vs. In-Memory
Date: 2011-05-05 15:47:11
Message-ID: 4DC2C67F.3040501@free.fr
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy pgsql-hackers

On 05/05/2011 17:36, Rob Wultsch wrote:
> On Thu, May 5, 2011 at 5:36 AM, Jehan-Guillaume (ioguix) de Rorthais
> <ioguix(at)free(dot)fr> wrote:
>> Yeah, but volatile means « lost on shutdown », which is not the case here
>> during a clean shutdown.
>
> Isn't that how the table should be treated though?

sure.

But imho, this "volatile tables" implies too many wrong ideas:

* lost on clean shutdown
* only in memory (sounds familiar)
* not on disk

In response to

Responses

Browse pgsql-advocacy by date

  From Date Subject
Next Message Joshua Berkus 2011-05-05 17:09:46 Re: Unlogged vs. In-Memory
Previous Message Rob Wultsch 2011-05-05 15:36:33 Re: Unlogged vs. In-Memory

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2011-05-05 15:54:01 Re: adding a new column in IDENTIFY_SYSTEM
Previous Message Rob Wultsch 2011-05-05 15:36:33 Re: Unlogged vs. In-Memory