Re: Cannot Start Postgres After System Boot

From: Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com>
To: Rich Shepard <rshepard(at)appl-ecosys(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Cannot Start Postgres After System Boot
Date: 2010-10-21 18:25:25
Message-ID: 4CC08595.7050005@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 10/21/2010 11:21 AM, Rich Shepard wrote:
> On Thu, 21 Oct 2010, Scott Marlowe wrote:
>
>> WHOA, never delete those files unless you're sure you've killed off
>> postgres first. Then and only then you can delete them and safely
>> restart. If you ever manage to bring up two postmasters on the same store
>> you've just destroyed your database.
>
> Scott,
>
> Postgres has not been running. That's the problem I've been trying to
> solve. The only reason I've manually killed the socket and its lock is when
> the system shut down uncleanly and postgres would not start while they were
> present.
>
> Thanks,
>
> Rich
>
>

But it is running:

rshepard(at)salmo ~]$ psql -h localhost -l
List of databases
Name | Owner | Encoding -----------+------------+----------
aesi | sql-ledger | LATIN1
cms | rshepard | UTF8
postgres | postgres | UTF8
refdb | postgres | UTF8
scirefs | rshepard | LATIN1
template0 | postgres | UTF8
template1 | postgres | UTF8

The missing piece of information seems to be the system board failure.
My guess is that caused corruption. See if you can connect by doing:

psql -h localhost -d aesi

--
Adrian Klaver
adrian(dot)klaver(at)gmail(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Rich Shepard 2010-10-21 18:38:58 Re: Cannot Start Postgres After System Boot
Previous Message Rich Shepard 2010-10-21 18:21:15 Re: Cannot Start Postgres After System Boot