"Meetesh Karia" <[EMAIL PROTECTED]> writes:
> ... But, once again we ran into the same
> situation where a query that normally executes in ~15ms wouldn't finish. As
> before, there were no ungranted locks and threads weren't waiting on a
> lock. I attached gdb to one of the stuck postgres process
Hi all,I just saw another email on the mailing list to this effect as well. We recently updated the kernel versions on our machines to the latest stable versions (which contained both HyperThreading and IO bug fixes) and we updated Postgres to version
8.0.8. We thought we were in the clear when
Hi Craig,Thanks for your response. This did start recently and it wasn't after a kernel update, but it was after we moved the db from Machine B to Machine A (which have slightly different kernel versions). However, the problem took about a week to show up after we moved from one machine to the ot
Meetesh Karia wrote:
Hi all,
We've recently started having a problem where a query that normally
executes in ~15ms starts to take upwards of 20s to complete. When the
connection that ran query is returned to the connection pool, it appears
as though a transaction is still in progress so the
Hi all,We've recently started having a problem where a query that normally executes in ~15ms starts to take upwards of 20s to complete. When the connection that ran query is returned to the connection pool, it appears as though a transaction is still in progress so the connection pool tries to can
