X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 48E9ED1B252 for ; Thu, 5 Aug 2004 16:13:17 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 62327-07 for ; Thu, 5 Aug 2004 19:13:09 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 5BBA0D1B1AC for ; Thu, 5 Aug 2004 16:13:06 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i75JD6Dw020261; Thu, 5 Aug 2004 15:13:06 -0400 (EDT) To: "Kevin Izzet" Cc: pgsql-admin@postgresql.org Subject: Re: psql won't stayed connected In-reply-to: References: Comments: In-reply-to "Kevin Izzet" message dated "Thu, 05 Aug 2004 17:05:32 +0100" Date: Thu, 05 Aug 2004 15:13:06 -0400 Message-ID: <20260.1091733186@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200408/24 X-Sequence-Number: 14419 "Kevin Izzet" writes: > Aug 5 17:01:38 uklnx04 postgres[28522]: [230-1] DEBUG: 00000: > InitPostgres > Aug 5 17:01:38 uklnx04 postgres[28522]: [230-2] LOCATION: PostgresMain, > postgres.c:2639 > Aug 5 17:01:38 uklnx04 postgres[28522]: [231-1] DEBUG: 00000: > proc_exit(0) > Aug 5 17:01:38 uklnx04 postgres[28522]: [231-2] LOCATION: proc_exit, > ipc.c:95 That's pretty bizarre ... I didn't think there were any code paths that would get to proc_exit without emitting an error message. Can you set a debugger breakpoint at proc_exit and see what the call stack looks like? (You can slow things down enough to attach to the backend with gdb by using the -W switch: PGOPTIONS="-W 30" psql ... regards, tom lane