Re: Survey on backing up unlogged tables: help us with PostgreSQL development! - Mailing list pgsql-general

From Andy Colson
Subject Re: Survey on backing up unlogged tables: help us with PostgreSQL development!
Date
Msg-id 4CE33015.5020909@squeakycode.net
Whole thread Raw
In response to Survey on backing up unlogged tables: help us with PostgreSQL development!  (Josh Berkus <josh@agliodbs.com>)
Responses Re: Survey on backing up unlogged tables: help us with PostgreSQL development!  (Josh Berkus <josh@agliodbs.com>)
List pgsql-general
On 11/16/2010 04:46 PM, Josh Berkus wrote:

> PostgreSQL 9.1 is likely to have, as a feature, the ability to create
> tables which are "unlogged", meaning that they are not added to the
> transaction log, and will be truncated (emptied) on database restart.
> Such tables are intended for highly volatile, but not very valuable,
> data, such as session statues, application logs, etc.

With the current patches, the data survives a restart just fine.

I'd like to vote for:
    safe restart = save data
    bad crashy restart = drop date

-Andy

pgsql-general by date:

Previous
From: Tomas Vondra
Date:
Subject: strange row count estimates with conditions on multiple column
Next
From: Glen Parker
Date:
Subject: Re: Survey on backing up unlogged tables: help us with PostgreSQL development!