| From: | Ron Mayer <rm_pg(at)cheapcomplexdevices(dot)com> |
|---|---|
| To: | Glen Parker <glenebob(at)nwlink(dot)com> |
| Cc: | PostgreSQL general <pgsql-general(at)postgresql(dot)org>, Josh Berkus <josh(at)agliodbs(dot)com> |
| Subject: | Re: Survey on backing up unlogged tables: help us with PostgreSQL development! |
| Date: | 2010-11-20 06:52:16 |
| Message-ID: | 4CE77020.3080309@cheapcomplexdevices.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Glen Parker wrote:
> As was already mentioned, application logs. Unlogged tables would be
> perfect for that, provided they don't go *poof* every now and then for
> no good reason. Nobody's going to be too heart broken if a handful of
> log records go missing, or get garbled, after a server crash or power
> outage. Delete 'em all after every restart though, and that's a problem.
How often are you doing unintentional restarts?
I'd guess for many people it's "whenever I had so many backend crashes
that I get motivated to check if I'm running the latest minor release".
And if it's an intentional restart - surely you could archive your
application logs before doing the restart, no?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Kellerer | 2010-11-20 09:13:07 | Re: newbie question - delete before insert |
| Previous Message | Grant Mckenzie | 2010-11-20 06:00:23 | newbie question - delete before insert |