Roberts, Jon wrote:
>> Tom Lane wrote:
>>> "Roberts, Jon" <Jon.Roberts@asurion.com> writes:
>>>> Version: "PostgreSQL 8.3.0, compiled by Visual C++ build 1400"
>>> Well, there are plenty of known bugs in 8.3.0 by now. You really
>>> should update before complaining, not after.
>> Yes. And the traditional question should be asked - is there any
>> antivirus or other "personal security" software running on tihs
> machine?
>> If so, uninstall (not just disable!) it and see if the problem goes
> away.
>
> I am not able to un-install this. However, this problem only started as
> the database grew in size and usage. It is 232 MB in size now and it
> has 30 or so active sessions 24x7.
But you do run antivirus on the machine? Which antivirus?
It's quite possible that this is the reason. As the files grow, the AV
may take longer to do whatever crap it's doing to them, thus exceeding
timeouts.
In general, you can get all sorts of strange things when you run AV on
your database server. The general recommendation is never to do that if
you want things to work, and it will be the first thing you're told to
remove.
It would be good if you could at least temporarily remove it and see if
it fixes the issue.
>> It would also be interesting to know if there are actually any other
>> processes running at this time.
>>
>
> Yes, there were about 30 active sessions executing functions.
Right, but are the processes still active at the moment whrere it
crashes, or has the postmaster managed to kill them off for the restart?
//Magnus