Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 2237F37C0C0 for ; Mon, 29 Sep 2008 14:52:53 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 98516-02 for ; Mon, 29 Sep 2008 14:52:46 -0300 (ADT) X-Greylist: delayed 00:06:39.624915 by SQLgrey-1.7.6 Received: from mail2.fluidhosting.com (mx24.fluidhosting.com [204.14.89.7]) by postgresql.org (Postfix) with ESMTP id 162A737D398 for ; Mon, 29 Sep 2008 14:45:45 -0300 (ADT) Received: (qmail 8958 invoked by uid 399); 29 Sep 2008 17:39:03 -0000 Received: from dsl-189-152-113-254.prod-infinitum.com.mx (HELO LENOVO670D2683) (189.152.113.254) by mail2.fluidhosting.com with ESMTPM; 29 Sep 2008 17:39:03 -0000 X-Originating-IP: 189.152.113.254 From: =?iso-8859-1?Q?Ing._Jorge_S_Alan=EDs_Garza?= To: Subject: PID file Date: Mon, 29 Sep 2008 12:43:54 -0500 Message-ID: <002201c9225a$f1a4cc00$d4ee6400$@alanis@blocknetworks.com.mx> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0023_01C92231.08CEC400" X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AckiWvEJxdK3IMAqR5i8fVWHU1IDXA== Content-Language: es-mx X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=1.212 tagged_above=0 required=5 tests=HTML_MESSAGE=0.001, MSGID_MULTIPLE_AT=1.211 X-Spam-Level: * X-Archive-Number: 200809/343 X-Sequence-Number: 30436 Este es un mensaje con varias partes en formato MIME. ------=_NextPart_000_0023_01C92231.08CEC400 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello, =20 We are operating Postgresql 8.2 on an ISCSI environment. Sometimes there = are issues with the ISCSI so Postgresql refuses to shutdown properly, or = start, because of the pid file. My question is, what is the correct thing to do with this pid file? On some test-environments I have deleted the pid and then when starting up, I see postgres complain about the database not shutting down cleanly. Is there a way to recover the non-working = postgres instance? Is this a very corruption-prone environment? =20 Thanks, =20 Jorge Santiago Alan=EDs Garza=20 Innovaci=F3n y Desarrollo=20 jorge.alanis@blocknetworks.com.mx Tel: (81) 4444.4044=20 Cel: (811) 243-6570 www.blocknetworks.com.mx=20 Av. L=E1zaro C=E1rdenas 4000, L-17=20 Col. Valle de las Brisas=20 Monterrey, Nuevo Le=F3n, CP 64790=20 Tel: +52 (81) 4444 4044 =20 =20 ------=_NextPart_000_0023_01C92231.08CEC400 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Hello,

We are operating Postgresql 8.2 = on an ISCSI environment. Sometimes there are issues with the ISCSI so Postgresql = refuses to shutdown properly, or start, because of the pid file. My question is, = what is the correct thing to do with this pid file? On some test-environments I = have deleted the pid and then when starting up, I see postgres complain about = the database not shutting down cleanly. Is there a way to recover the = non-working postgres instance? Is this a very corruption-prone = environment?

Thanks,

Jorge Santiago Alan=EDs Garza
Innovaci=F3n y Desarrollo
jorge.alanis@blocknetworks.c= om.mx

Tel: (81) 4444.4044
Cel: (811) 243-6570

www.blocknetworks.com.mx
Av. L=E1zaro C=E1rdenas 4000, L-17
Col. Valle de las Brisas
Monterrey, Nuevo Le=F3n, CP 64790
Tel: +52 (81) 4444 4044

------=_NextPart_000_0023_01C92231.08CEC400--