| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | David Johansen <davejohansen(at)gmail(dot)com> |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Auto-vacuum timing out and preventing connections |
| Date: | 2022-07-02 03:11:39 |
| Message-ID: | 20220702031139.3avsl64ivhjcnbaw@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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?
> 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.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Johansen | 2022-07-02 04:34:13 | Re: Auto-vacuum timing out and preventing connections |
| Previous Message | 396934406@qq.com | 2022-07-02 00:29:27 | Re: RE: pg15 beta2 bug:cause by logcial replation |