LWLockAcquire problems

From: Scott Shattuck <ss(at)technicalpursuit(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: LWLockAcquire problems
Date: 2002-08-14 03:03:17
Message-ID: 1029294198.7491.3854.camel@idearat
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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 other backend
died abnormally and possibly corrupted shared memory.
I have rolled back the current transaction and am
going to terminate your database system connection and exit.
Please reconnect to the database system 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.

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Hannu Krosing 2002-08-14 03:15:34 Re: OOP real life example (was Re: Why is MySQL more
Previous Message Bruce Momjian 2002-08-14 02:54:48 Re: Patch for "Bug of PL/pgSQL parser"