Re: unlogged tables

Steve Crawford <scrawford@pinpointresearch.com>

From: Steve Crawford <scrawford@pinpointresearch.com>

To: Tom Lane <tgl@sss.pgh.pa.us>

Cc: Andrew Dunstan <andrew@dunslane.net>, Kenneth Marshall <ktm@rice.edu>, Robert Haas <robertmhaas@gmail.com>, Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>, marcin mank <marcin.mank@gmail.com>, Andy Colson <andy@squeakycode.net>, pgsql-hackers@postgresql.org

Date: 2010-11-17T21:19:10Z

Lists: pgsql-hackers

On 11/17/2010 11:44 AM, Tom Lane wrote:
> ...because a backend crash has to be assumed to have corrupted 
> unlogged tables...
>    
So in a typical use-case, say storing session data on a web-site, one 
crashed backend could wreck sessions for some or all of the site? Is 
there a mechanism in the proposal that would allow a client to determine 
the state of a table (good, truncated, wrecked, etc.)?

Cheers,
Steve