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?
