| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Glen Parker <glenebob(at)nwlink(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:55:46 |
| Message-ID: | 4CE33622.8080109@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> 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.
--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2010-11-17 01:59:13 | Re: Survey on backing up unlogged tables: help us with PostgreSQL development! |
| Previous Message | Glen Parker | 2010-11-17 01:51:51 | Re: Survey on backing up unlogged tables: help us with PostgreSQL development! |