Re: Survey on backing up unlogged tables: help us with PostgreSQL development!

From: Andy Colson <andy(at)squeakycode(dot)net>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: PostgreSQL general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Survey on backing up unlogged tables: help us with PostgreSQL development!
Date: 2010-11-17 01:29:57
Message-ID: 4CE33015.5020909@squeakycode.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Glen Parker 2010-11-17 01:30:13 Re: Survey on backing up unlogged tables: help us with PostgreSQL development!
Previous Message Tomas Vondra 2010-11-17 01:17:42 strange row count estimates with conditions on multiple column