From: | Igor <igorya(dot)inscriptio(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #7670: BUG #7545: Unresponsive server with error log reporting: "poll() failed: Invalid argument" |
Date: | 2012-11-18 18:05:26 |
Message-ID: | CALdM5ephLEcp8xoViVvc13AWU8RhHYVGqRP2pd6Upok4eyEwkA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
2012/11/18 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
> Igor <igorya(dot)inscriptio(at)gmail(dot)com> writes:
> > 2012/11/18 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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>
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2012-11-18 18:06:54 | Re: BUG #7670: BUG #7545: Unresponsive server with error log reporting: "poll() failed: Invalid argument" |
Previous Message | Igor | 2012-11-18 17:55:57 | Re: BUG #7670: BUG #7545: Unresponsive server with error log reporting: "poll() failed: Invalid argument" |