From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | syspegasus(at)gmail(dot)com |
Cc: | PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: BUG #13990: Postgres shutting down automatically |
Date: | 2016-02-26 01:44:36 |
Message-ID: | CAB7nPqQ64X8oGhCPBRLJ6Yn3p7NC3xgFP5LLxxQLABTrgX__AA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Thu, Feb 25, 2016 at 9:10 PM, <syspegasus(at)gmail(dot)com> wrote:
> The following bug has been logged on the website:
>
> Bug reference: 13990
> Logged by: Talita
> Email address: syspegasus(at)gmail(dot)com
> PostgreSQL version: 9.4.5
> Operating system: Windows 7
> Description:
>
> Hi, I'm having problem with the postgres service.. randomly stop to
> working.. And to work again I have to wait a time, or restart the
> computer(and sometimes don't work too).. I'm using Windows 7.
>
> In the log appears:
> 2016-02-25 08:54:52 BRT WARNING: worker took too long to start; canceled
>
> I tried to unistall and install again, but the problem persist. I don't know
> more what to do..
There is no bug here, the error message you are seeing is a sign that
this node is CPU-starved and slow to start up an autovacuum process:
this prevents a worker to start should another one be in starting
state or failed to start.
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2016-02-26 07:16:34 | Re: BUG #13977: Strange behavior with WAL archive recovery |
Previous Message | Tom Lane | 2016-02-26 00:55:08 | Re: BUG #13988: "plan should not reference subplan's variable" whilst using row level security |