From: | Alban Hertroys <dalroi(at)solfertje(dot)student(dot)utwente(dot)nl> |
---|---|
To: | <A(dot)Bhattacharya(at)sungard(dot)com> <A(dot)Bhattacharya(at)sungard(dot)com> |
Cc: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: WARNING: worker took too long to start; cancelled on VACCUM ANALYZE |
Date: | 2009-12-01 10:29:37 |
Message-ID: | 92E91A68-347A-4C1C-B778-83DC01F2FC42@solfertje.student.utwente.nl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 1 Dec 2009, at 11:00, <A(dot)Bhattacharya(at)sungard(dot)com> <A(dot)Bhattacharya(at)sungard(dot)com> wrote:
> Hi All,
>
> I am facing the below error when executing "VACCUM ANALYZE" on the
> several tables and also the entire PostgreSQL database hanging up and
> not responding.
>
> WARNING: worker took too long to start; cancelled
>
> I have disabled my AV and I have the modified the below parameters in
If I recall correctly Windows doesn't have sockets so the connection is made using the loopback device. Maybe the worker process isn't allowed to connect and after a while it times out trying?
If it's not that, there is a good chance that your AV software installed all kinds of hooks that can subtly change the behaviour of system functions. If that's the case disabling it is not enough, you should try to uninstall it and hope it removes all the hooks.
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll see there is no forest.
!DSPAM:737,4b14f01211735785317057!
From | Date | Subject | |
---|---|---|---|
Next Message | Sam Jas | 2009-12-01 10:40:10 | Re: WARNING: worker took too long to start; cancelled on VACCUM ANALYZE |
Previous Message | A.Bhattacharya | 2009-12-01 10:00:52 | WARNING: worker took too long to start; cancelled on VACCUM ANALYZE |