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

Re: Unlogged vs. In-Memory

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Josh Berkus" <josh(at)agliodbs(dot)com>,"Thom Brown" <thom(at)linux(dot)com>
Cc: "damien clochard" <damien(at)dalibo(dot)info>, "Jehan-Guillaume (ioguix) de Rorthais" <ioguix(at)free(dot)fr>, "Rob Wultsch" <wultsch(at)gmail(dot)com>, <pgsql-advocacy(at)postgresql(dot)org>, "Roy Hann" <specially(at)processed(dot)almost(dot)meat>
Subject: Re: Unlogged vs. In-Memory
Date: 2011-05-05 18:27:03
Message-ID: 4DC2A5A7020000250003D30F@gw.wicourts.gov (view raw or flat)
Thread:
Lists: pgsql-advocacypgsql-hackers
Josh Berkus <josh(at)agliodbs(dot)com> wrote:
 
> So far, the only suggestions I've seen for how to advocate this
> feature have involved renaming it, which isn't realistic at this
> point.
 
Agreed; we are talking about describing it concisely.
 
> If someone has an alternative description for the feature that
> anyone who is not already a PostgreSQL DBA will care about, them
> please come forward with it.
 
The similarities to a GLOBAL TEMPORARY TABLE are striking enough
that perhaps it should play off that somehow.  It is a lot like a
SHARED GLOBAL TEMPORARY TABLE.  The only thing to add to that is
that on a clean shutdown the system will save the contents for
reload on startup, whereas a crash will clear it.
 
-Kevin

In response to

pgsql-hackers by date

Next:From: Thom BrownDate: 2011-05-05 18:28:23
Subject: Re: Unlogged vs. In-Memory
Previous:From: Josh BerkusDate: 2011-05-05 18:17:33
Subject: Re: Unlogged vs. In-Memory

pgsql-advocacy by date

Next:From: Thom BrownDate: 2011-05-05 18:28:23
Subject: Re: Unlogged vs. In-Memory
Previous:From: Josh BerkusDate: 2011-05-05 18:17:33
Subject: Re: Unlogged vs. In-Memory

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