| From: | Andy Colson <andy(at)squeakycode(dot)net> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | Glen Parker <glenebob(at)nwlink(dot)com>, 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:59:35 |
| Message-ID: | 4CE33707.8060802@squeakycode.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 11/16/2010 07:55 PM, Josh Berkus wrote:
>
>> If you do wish to have the data tossed out for no good reason every so
>> often, then there ought to be a separate attribute to control that. I'm
>> really having trouble seeing how such behavior would be desirable enough
>> to ever have the server do it for you, on its terms rather than yours.
>
> I don't quite follow you. The purpose of unlogged tables is for data
> which is disposable in the event of downtime; the classic example is the
> a user_session_status table. In the event of a restart, all user
> sessions are going to be invalid anyway.
>
Why? If you dont blow away the sessions table, everything should be fine.
-Andy
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Glen Parker | 2010-11-17 02:47:39 | Re: Survey on backing up unlogged tables: help us with PostgreSQL development! |
| Previous Message | Josh Berkus | 2010-11-17 01:59:13 | Re: Survey on backing up unlogged tables: help us with PostgreSQL development! |