| From: | David Johansen <davejohansen(at)gmail(dot)com> |
|---|---|
| To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
| Cc: | pgsql-bugs <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Auto-vacuum timing out and preventing connections |
| Date: | 2022-07-14 16:51:39 |
| Message-ID: | CAAcYxUc3rBb_F_b5r5Mr3vnP6eYa5bgob072_F3+Fh2d-CLbQA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Tue, Jun 28, 2022 at 2:05 PM David Johansen <davejohansen(at)gmail(dot)com>
wrote:
> On Tue, Jun 28, 2022 at 1:31 PM Jeff Janes <jeff(dot)janes(at)gmail(dot)com> wrote:
>
>> On Mon, Jun 27, 2022 at 4:38 PM David Johansen <davejohansen(at)gmail(dot)com>
>> wrote:
>>
>>> We're running into an issue where the database can't be connected to. It
>>> appears that the auto-vacuum is timing out and then that prevents new
>>> connections from happening. This assumption is based on these logs showing
>>> up in the logs:
>>> WARNING: worker took too long to start; canceled
>>> The log appears about every 5 minutes and eventually nothing can connect
>>> to it and it has to be rebooted.
>>>
>>
>> As Julien suggested, this sounds like another victim, not the cause. Is
>> there anything else in the log files?
>>
>
> That's the only thing in the logs for the 12-24 hours before the database
> becomes inaccessible.
>
To follow up on this, this was the symptom and not the cause. The
auto-vacuum was failing to start because of a bug and not the cause of the
problem.
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Francisco Olarte | 2022-07-14 16:51:54 | Re: BUG #17550: inet type doesn't accept alternate notations of ipv4 addresses |
| Previous Message | PG Bug reporting form | 2022-07-14 14:49:05 | BUG #17550: inet type doesn't accept alternate notations of ipv4 addresses |