From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: 'startup waiting' status message |
Date: | 2006-08-07 03:53:43 |
Message-ID: | 9384.1154922823@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Jim C. Nasby" <jnasby(at)pervasive(dot)com> writes:
> postgres 2038 0.0 0.2 19628 3328 ? S 15:04 0:00 postgres:
> aspadmin test 192.168.100.7(34223) startup waiting
> I've grepped through the source code (grep -ri startup src|grep -i
> waiting) and can't find this anywhere...
You wouldn't, because that's a composite of two messages: we are waiting
for some lock while still in startup mode. A reasonable bet is that
someone's got a more-or-less-exclusive lock on one of the system
catalogs that startup needs to read. The contents of pg_locks would
help, if this state persists long enough to investigate ...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | ITAGAKI Takahiro | 2006-08-07 04:36:56 | Re: CSStorm occurred again by postgreSQL8.2 |
Previous Message | Tom Lane | 2006-08-07 03:50:06 | Re: LWLock statistics collector |