| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Pete Leonard <pete(at)hero(dot)com> |
| Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Re: sick DB - ?? |
| Date: | 2001-07-18 18:10:20 |
| Message-ID: | 8835.995479820@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Pete Leonard <pete(at)hero(dot)com> writes:
>> restart didn't bring the DB back properly, so as the postgres user, did
>> the following:
>> /usr/local/pgsql/bin/postmaster -d5 start
>> it dumps the initial environment variables, and then returns nothing. CPU
>> is pegged at 100%. No reporting, no information as to what's happening.
This is kind of a random guess, but we recently noticed that 7.1 has a
bug whereby the postmaster can go into an infinite loop at startup if
the $PGDATA directory is not writable. Check permissions. It might
also be a good idea to remove the old postmaster.pid file by hand.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephan Szabo | 2001-07-18 18:17:38 | Re: VACUUM ANALYZE |
| Previous Message | will trillich | 2001-07-18 17:58:34 | Re: Errors in logs |