Hanging queries on Windows 2003 SP1

Started by Wei Songover 19 years ago3 messagesbugs
Jump to latest
#1Wei Song
weisong44@gmail.com

Hi,

We are seeing hanging queries on Windows 2003 Server SP1 with dual CPU,
looks like one of the process is blocked. In a lot of cases, the whole
DB is blocked if this process is holding important locks.

Looks like this issue was discussed in the following thread a few month
ago, but didn't seem to have a solution mention. I would liek to know
if there is a patch for this already?

http://archives.postgresql.org/pgsql-performance/2006-03/msg00129.php

I would appreciate your feedbaek,

Thanks,
Wei

#2Magnus Hagander
magnus@hagander.net
In reply to: Wei Song (#1)
Re: Hanging queries on Windows 2003 SP1

Hi,

We are seeing hanging queries on Windows 2003 Server SP1 with dual
CPU, looks like one of the process is blocked. In a lot of cases,
the whole DB is blocked if this process is holding important locks.

Looks like this issue was discussed in the following thread a few
month ago, but didn't seem to have a solution mention. I would liek
to know if there is a patch for this already?

http://archives.postgresql.org/pgsql-performance/2006-
03/msg00129.php

There have been some fairly extensive changes in the semaphore code for
8.2. Any chance you can try the cvs snapshot version and see if the
problem exists there as well?

//Magnus

#3Wei Song
weisong44@gmail.com
In reply to: Magnus Hagander (#2)
Re: Hanging queries on Windows 2003 SP1

Hi Magnus,

Sure, I could try that out. Is there a place to download a 8.2 image to
bypass setting up the tool chain?

-Wei

Show quoted text

On 9/4/06, Magnus Hagander <mha@sollentuna.net> wrote:

Hi,

We are seeing hanging queries on Windows 2003 Server SP1 with dual
CPU, looks like one of the process is blocked. In a lot of cases,
the whole DB is blocked if this process is holding important locks.

Looks like this issue was discussed in the following thread a few
month ago, but didn't seem to have a solution mention. I would liek
to know if there is a patch for this already?

http://archives.postgresql.org/pgsql-performance/2006-
03/msg00129.php

There have been some fairly extensive changes in the semaphore code for
8.2. Any chance you can try the cvs snapshot version and see if the
problem exists there as well?

//Magnus