Hello,
We are running Postgres 7.0.2 on Linux RH 6.2 Dell servers.
When traffic gets heavy we often get one of the backend locked up in an
UPDATE, INSERT or COMMIT request. Eventually all the other backends end
up locking too as they try to access a row locked by the original
backend. The out
Brian J. France wrote:
>
> BTW, on a different table I get this warning ever time I vacuum the
database. It doesn't seem to cause a problem, but didn't know how to get
rid of it.
>
> NOTICE: Index : NUMBER OF INDEX' TUPLES (214) IS NOT THE
SAME AS HEAP' (215).
> Recreate the index
Hi Tom,
[EMAIL PROTECTED]">"Brian J. France" <[EMAIL PROTECTED]> writes:
I am getting a few of these errors in my web logs and didn't know what I could do to stop it.
NOTICE: Deadlock detected -- See the lock(l) manual page for a possible cause.
Error in query "UPDATE SET = WHER
