| From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
|---|---|
| To: | "Simon Riggs" <simon(at)2ndQuadrant(dot)com>, "Robert Haas" <robertmhaas(at)gmail(dot)com> |
| Cc: | "Joshua Berkus" <josh(at)agliodbs(dot)com>, "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, "Rob Wultsch" <wultsch(at)gmail(dot)com>, "Magnus Hagander" <magnus(at)hagander(dot)net>, "Thom Brown" <thom(at)linux(dot)com>, "PostgreSQL Advocacy" <pgsql-advocacy(at)postgresql(dot)org> |
| Subject: | Re: Unlogged vs. In-Memory |
| Date: | 2011-05-05 19:09:09 |
| Message-ID: | 4DC2AF85020000250003D328@gw.wicourts.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy pgsql-hackers |
Simon Riggs <simon(at)2ndQuadrant(dot)com> wrote:
> I doubt that anyone wants the current behaviour.
Current behavior would be an exact fit for a few use cases we have.
Attempting to salvage some portion of the data on startup after a
crash would yield it unusable for the uses I have in mind. It would
have either all be there, or all gone.
That's not to knock use cases others may have, just providing a data
point.
-Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2011-05-05 19:10:48 | Re: Unlogged vs. In-Memory |
| Previous Message | Simon Riggs | 2011-05-05 19:00:51 | Re: Unlogged vs. In-Memory |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2011-05-05 19:10:48 | Re: Unlogged vs. In-Memory |
| Previous Message | Simon Riggs | 2011-05-05 19:00:51 | Re: Unlogged vs. In-Memory |