| From: | Glen Parker <glenebob(at)nwlink(dot)com> |
|---|---|
| To: | PostgreSQL general <pgsql-general(at)postgresql(dot)org> |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Subject: | Re: Survey on backing up unlogged tables: help us with PostgreSQL development! |
| Date: | 2010-11-17 01:51:51 |
| Message-ID: | 4CE33537.3070107@nwlink.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 11/16/2010 05:33 PM, Josh Berkus wrote:
>
>> With the current patches, the data survives a restart just fine.
>
> Per -hackers, that's not guarenteed.
>
Which is fine. If you choose to set a table to nonlogged, that implies
that you accept the risk of corrupted data, or that you don't "get it",
in which case . It should not however, imply that you want it all
thrown out every so often for no good reason.
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.
-Glen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2010-11-17 01:55:46 | Re: Survey on backing up unlogged tables: help us with PostgreSQL development! |
| Previous Message | Scott Mead | 2010-11-17 01:45:27 | Re: Survey on backing up unlogged tables: help us with PostgreSQL development! |