Re: Unlogged vs. In-Memory - Mailing list pgsql-advocacy

From Thom Brown
Subject Re: Unlogged vs. In-Memory
Date
Msg-id BANLkTimHde7gZHQu9Tn4TWF0LjFwL6Dd9g@mail.gmail.com
Whole thread Raw
In response to Re: Unlogged vs. In-Memory  (Joshua Berkus <josh@agliodbs.com>)
Responses Re: Unlogged vs. In-Memory  (Josh Berkus <josh@agliodbs.com>)
List pgsql-advocacy
On 5 May 2011 18:09, Joshua Berkus <josh@agliodbs.com> wrote:
> All,
>
> FWIW, I wasn't planning to change the name of the feature (although Volatile Tables has a certain appeal).   We also
havea duty to our users not to mislead them, and "Unlogged tables" does say something about the durability of their
data.  The last thing we want is for users to repeat the MyISAM experience with PostgreSQL.  Also, we're not changing
thesyntax for declaring one at this point. 
>
> My query to this list was mostly about how we *describe* Unlogged Tables for the press.  I have the same questions
abouta few other features, but we seem to have hammered out SSI. 
>
> I feel like the consensus is that we can describe Unlogged Tables as "similar to in-memory tables" without misleading
anyone.

Saying "similar to in-memory tables" sounds immediately misleading to
me.  If I didn't know any better, I'd assume:

- the table is kept in memory
- no data ever written to disk
- all data lost upon stopping the service

None of these are true.

Thom

pgsql-advocacy by date:

Previous
From: Joshua Berkus
Date:
Subject: Re: Unlogged vs. In-Memory
Next
From: Jeff Davis
Date:
Subject: ubuntu software center