| From: | Bruce Lowery <bruce(dot)lowery(at)edventions(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | deadlock in 6.4.2 |
| Date: | 1999-11-24 18:47:33 |
| Message-ID: | 383C32C5.1936A174@edventions.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hello,
I've noticed some previous postings about deadlocks in 6.4.2. At the
risk of being irritating, I'd like to ask if anyone has seen this
particular version of the problem: postmaster deadlocks leaving
multiple ZOMBIE children with something like the following in the log
file:
NOTICE: Deadlock detected -- See the lock(l) manual page for a possible
cause.
ERROR: WaitOnLock: error on wakeup - Aborting this transaction
NOTICE: Deadlock detected -- See the lock(l) manual page for a possible
cause.
ERROR: WaitOnLock: error on wakeup - Aborting this transaction
ERROR: postmaster: StreamConnection: accept: Too many open files in
system
The suggested (and acceptable) solution seems to be to move to 6.5.x,
but I'd hoped to get confirmation others had seen such - the 'too many
open files' seemed new.
Bruce Lowery
Edventions.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sean Carmody | 1999-11-24 22:28:08 | |
| Previous Message | Nikos Mouat | 1999-11-24 18:01:41 | FORIEGN KEY's, JOIN's, and others |