2012/11/18 Tom Lane <t...@sss.pgh.pa.us> > Igor <igorya.inscrip...@gmail.com> writes: > > 2012/11/18 Tom Lane <t...@sss.pgh.pa.us> > >> I was just about to ask what you have log_rotation_age set to ... > > > Was: > > log_rotation_age = 30d > > That's the problem then. Internally that gets converted to > milliseconds, which'll overflow at 24-something days. Use a smaller > value. > > So the actual bug here is an over-optimistic maximum value for > log_rotation_age in guc.c. After looking through all the callers of > WaitLatch, I think the only other similar issue is for > wal_sender_timeout, which currently is allowed to range up to INT_MAX; > but such values seem pretty useless. > > I'm inclined to propose limiting both of these to the equivalent of 15 > days.
# Set this options to: logging_collector = on log_rotation_age = 15d log_rotation_size = 100MB # was early And will watch.. -- Regards System and web developer. <http://amkmobile.com>
