Re: Bug #948: Postgresql server abruptly shutdown now data - Mailing list pgsql-bugs

From SALUNKHE,MANDAR (HP-Singapore,ex1)
Subject Re: Bug #948: Postgresql server abruptly shutdown now data
Date
Msg-id B2CFBDADA593FE4D9BD360111FB7F231068D4D73@xsg01.sgp.hp.com
Whole thread Raw
List pgsql-bugs
Dear Tom,
Thanks for your reply.
We have rebooted the server and checked if there is any pid for ipc-daemon
but there was none.
Is there any other way to check for "if it has any on-disk state that needs
to be cleaned up."?
Please do reply as the matter is critical.

Thanks

Mandar Salunkhe
460 Alexandra Road, PSA Building
Singapore 119963
Phone: 65-63617413      HP Telnet Number: 831-7413
Email: mandar.salunkhe@hp.com

-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us <mailto:tgl@sss.pgh.pa.us> ]
Sent: Thursday, April 17, 2003 10:48 PM
To: mandar.salunkhe@hp.com; pgsql-bugs@postgresql.org
Subject: Re: [BUGS] Bug #948: Postgresql server abruptly shutdown now
database doesnt start


pgsql-bugs@postgresql.org writes:
> But now when we run this , we get

> hp@ACACIA ~
> $ cd /usr/local/pgsql/bin/

> hp@ACACIA /usr/local/pgsql/bin
> $ ipc-daemon &
> [1] 18140

> hp@ACACIA /usr/local/pgsql/bin
> $ ./postmaster -i -D /usr/local/pgsql/data

> And the process hangs there.

I'd have to guess that something is wrong with ipc-daemon.  You should look
to see if it has any on-disk state that needs to be cleaned up.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Joe Slag
Date:
Subject: 7.1 -> 7.3 migration timestamp problem
Next
From: "SALUNKHE,MANDAR (HP-Singapore,ex1)"
Date:
Subject: Re: Bug #948: Postgresql server abruptly shutdown now data