[copying this one over to hackers]
> Our DBAs reviewed the Microsoft documentation you referenced,
> modified the registry, and rebooted the OS. We've been
> beating up on the database without seeing the error so far.
> We'll keep at it for a while.
Very interesting. As this seems to be a resource error, a couple of
questions. Sorry if you've already answered some of them, couldn't find
it in the archives.
1) Is this a dedicated pg server, or does it have something else on it?
2) We have to ask this - do you run any antivirus on it, that might nto
be releasing resources the right way? Anything else that might stick in
a kernel driver?
3) Are you hitting the database with many connections, or is this a
single/few connection scenario? Are the other connections typically
active when this shows up?
Seems like we could just retry when we get this failure. The question is
we need to do a small amount of sleep before we do? Also, we can't just
retry forever, there has to be some kind of end to it...
(If you read the SQL kb, it can be read as retrying is the correct
thing, because the bug in sql was that it didn't retry)
pgsql-hackers by date
|Next:||From: Andreas Pflug||Date: 2005-11-17 09:57:01|
|Subject: Re: Numeric 508 datatype|
|Previous:||From: Tom Lane||Date: 2005-11-17 05:51:47|
|Subject: Re: OS X 7.4 failure |
pgsql-admin by date
|Next:||From: Colton A Smith||Date: 2005-11-17 13:20:12|
|Subject: fsm allocation|
|Previous:||From: Wim Bertels||Date: 2005-11-16 22:50:35|
|Subject: Re: md5 collision generator|