Re: Auto-vacuum timing out and preventing connections
От | Andres Freund |
---|---|
Тема | Re: Auto-vacuum timing out and preventing connections |
Дата | |
Msg-id | 20220715034218.2lzzqdqemafnqd7e@awork3.anarazel.de обсуждение исходный текст |
Ответ на | Re: Auto-vacuum timing out and preventing connections (David Johansen <davejohansen@gmail.com>) |
Ответы |
Re: Auto-vacuum timing out and preventing connections
|
Список | pgsql-bugs |
Hi, On 2022-07-14 10:51:39 -0600, David Johansen wrote: > On Tue, Jun 28, 2022 at 2:05 PM David Johansen <davejohansen@gmail.com> > wrote: > > > On Tue, Jun 28, 2022 at 1:31 PM Jeff Janes <jeff.janes@gmail.com> wrote: > > > >> On Mon, Jun 27, 2022 at 4:38 PM David Johansen <davejohansen@gmail.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. What bug? Greetings, Andres Freund
В списке pgsql-bugs по дате отправления: