Re: Auto-vacuum timing out and preventing connections

From: David Johansen <davejohansen(at)gmail(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: pgsql-bugs <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: Auto-vacuum timing out and preventing connections
Date: 2022-07-02 04:34:13
Message-ID: CAAcYxUeJKDkYqoXYe6qwHRP_QEif7O083U2p0FKzoUXVLxHn4Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, Jul 1, 2022 at 9:11 PM Andres Freund <andres(at)anarazel(dot)de> wrote:

> Hi,
>
> On 2022-06-27 14:38:21 -0600, David Johansen 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.
>
> How many databases, tables and functions do you have?
>

1 database
427 tables
1 function

> > What can we do to diagnose this problem and get our database working
> > reliably again?
>
> Downthread you said you're on RDS - unfortunately you're going to have
> quite
> limited access and are going to have to take it up with AWS.
>

Yes, I definitely understand that AWS will likely need to be involved or
resolve this issue, but as I said previously, I'm trying to be proactive
and just see what I could find.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Hung Nguyen 2022-07-02 12:15:55
Previous Message Andres Freund 2022-07-02 03:11:39 Re: Auto-vacuum timing out and preventing connections