LWLockAcquire problems - Mailing list pgsql-hackers

From Scott Shattuck
Subject LWLockAcquire problems
Date
Msg-id 1029294198.7491.3854.camel@idearat
Whole thread Raw
Responses Re: LWLockAcquire problems  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
I posted this earlier but it didn't seem to go through. I apologize in
advance if you've gotten this twice. Since I posted earlier this error
happened 2 additional times. It's now a critical issue for our site:



I'm seeing the following error about once a week or so:

2002-08-13 12:37:28 [24313]  FATAL 1:  LWLockAcquire: can't wait without
a PROC structure


It's usually preceded by these:

2002-08-13 12:37:28 [24313]  FATAL 1:  Database "template0" is not
currently accepting connections


And immediately followed by this:

2002-08-13 12:37:28 [12532]  DEBUG:  server process (pid 24313) exited
with exit code 1
2002-08-13 12:37:28 [12532]  DEBUG:  terminating any other active server
processes


All active database processes then immediately do the following:

2002-08-13 12:37:28 [24311]  NOTICE:  Message from PostgreSQL backend:       The Postmaster has informed me that some
otherbackend       died abnormally and possibly corrupted shared memory.       I have rolled back the current
transactionand am       going to terminate your database system connection and exit.       Please reconnect to the
databasesystem and repeat your query.
 


Ouch!

Any idea what's going on here? Is the LWLockAcquire related to something
like the size of the lock table or something? Any help on eliminating
this error would be appreciated. Thanks!


ss

Scott Shattuck
Technical Pursuit Inc.





pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Patch for "Bug of PL/pgSQL parser"
Next
From: "Marc G. Fournier"
Date:
Subject: Re: anoncvs currently broken