Skip site navigation (1) Skip section navigation (2)

Re: Unlogged vs. In-Memory

From: Thom Brown <thom(at)linux(dot)com>
To: Joshua Berkus <josh(at)agliodbs(dot)com>
Cc: "Jehan-Guillaume (ioguix) de Rorthais" <ioguix(at)free(dot)fr>, damien clochard <damien(at)dalibo(dot)info>, Roy Hann <specially(at)processed(dot)almost(dot)meat>, pgsql-advocacy(at)postgresql(dot)org, Rob Wultsch <wultsch(at)gmail(dot)com>
Subject: Re: Unlogged vs. In-Memory
Date: 2011-05-05 17:15:15
Message-ID: BANLkTimHde7gZHQu9Tn4TWF0LjFwL6Dd9g@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-advocacypgsql-hackers
On 5 May 2011 18:09, Joshua Berkus <josh(at)agliodbs(dot)com> wrote:
> All,
>
> FWIW, I wasn't planning to change the name of the feature (although Volatile Tables has a certain appeal).   We also have a 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 the syntax 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 about a 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

In response to

Responses

pgsql-hackers by date

Next:From: Andrew DunstanDate: 2011-05-05 17:19:29
Subject: Re: VARIANT / ANYTYPE datatype
Previous:From: Magnus HaganderDate: 2011-05-05 17:14:10
Subject: Re: FDW table hints

pgsql-advocacy by date

Next:From: Jeff DavisDate: 2011-05-05 17:20:56
Subject: ubuntu software center
Previous:From: Joshua BerkusDate: 2011-05-05 17:09:46
Subject: Re: Unlogged vs. In-Memory

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group