On Sun, Dec 02, 2018 at 12:09:57PM -0500, Tom Lane wrote: > Arkhena <arkh...@gmail.com> writes: > > As a consultant with so many customers that simply install Postgres "out of > > the box", I think that changing log_destination to 'csvlog' and > > logging_collector to 'on' needs changing at least log_truncate_on_rotation > > (but certainly also log_filename and log_rotation_age) if we don't want my > > customers to run out of space sooner or later. > > Yeah, that's another issue that we'd have to confront if we turn > logging_collector on by default: the default settings for log > rotation aren't exactly foolproof, and we'd need to make them so. > > (Now having said that, the default setup *without* logging_collector > isn't exactly foolproof either, since wherever you send stderr to > will grow without bound. But maybe people are used to dealing with > that.) > > Independently of changing logging_collector's default, perhaps we could > agree on changes to the rotation-related defaults so that it's less > risky to just turn logging_collector on without other changes?
Would rotating daily and keeping a week's worth be reasonable as defaults? If not, what do you have in mind? Best, David. -- David Fetter <david(at)fetter(dot)org> http://fetter.org/ Phone: +1 415 235 3778 Remember to vote! Consider donating to Postgres: http://www.postgresql.org/about/donate
