| 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 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy pgsql-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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thom Brown | 2011-05-05 18:28:23 | Re: Unlogged vs. In-Memory |
| Previous Message | Josh Berkus | 2011-05-05 18:17:33 | Re: Unlogged vs. In-Memory |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thom Brown | 2011-05-05 18:28:23 | Re: Unlogged vs. In-Memory |
| Previous Message | Josh Berkus | 2011-05-05 18:17:33 | Re: Unlogged vs. In-Memory |