Re: LWLockAcquire problems

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Scott Shattuck <ss(at)technicalpursuit(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: LWLockAcquire problems
Date: 2002-08-14 04:42:25
Message-ID: 4693.1029300145@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Scott Shattuck <ss(at)technicalpursuit(dot)com> writes:
> 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

Oh? I'd love to see what makes this happen. Can you give more context?

> It's usually preceded by these:
> 2002-08-13 12:37:28 [24313] FATAL 1: Database "template0" is not
> currently accepting connections

That's interesting but I'm not sure it proves much. If I try to connect
to template0 here, I only see the "not currently accepting connections"
message, not any LWLock complaints. So I think there's more to it...

> And immediately followed by this:
> 2002-08-13 12:37:28 [12532] DEBUG: server process (pid 24313) exited
> with exit code 1

That's just the effects of the FATAL 1 exit (see my comments to Tom
O'Connell earlier today).

The "can't wait without a PROC" failure suggests strongly that something
is rotten in very early backend startup --- once MyProc has been set,
it won't happen, and *darn* little happens before MyProc gets set.
But I'm not sure how to proceed beyond that observation. If you can
offer any context or information at all, it'd be helpful.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2002-08-14 04:42:48 Re: [HACKERS] tsearch vs. fulltextindex
Previous Message Bruce Momjian 2002-08-14 04:42:09 Re: OOP real life example (was Re: Why is MySQL more