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 7A5FD5E46C7 for ; Fri, 6 Aug 2004 13:40:24 -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 25608-07 for ; Fri, 6 Aug 2004 16:40:27 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id B5F225E46CB for ; Fri, 6 Aug 2004 13:40:18 -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 i76GePkX020231; Fri, 6 Aug 2004 12:40:25 -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 "Fri, 06 Aug 2004 16:32:04 +0100" Date: Fri, 06 Aug 2004 12:40:25 -0400 Message-ID: <20230.1091810425@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/34 X-Sequence-Number: 14429 "Kevin Izzet" writes: > Managed to get the debugger to work and here are the results, don't > understand the results mind :-) > #0 0x08155d55 in proc_exit () > #1 0x08161c17 in PostgresMain () > #2 0x0813eee0 in BackendFork () > #3 0x0813e8d6 in BackendStartup () Hmph. Well, AFAICS the only way for PostgresMain to call proc_exit() directly is if it's seen EOF from the client (ie, connection closure). So what you've really got is either a broken copy of psql on the Solaris machine, or some kind of network issue that's causing the connection to be closed almost immediately after establishment. The latter seems a bit odd, since at the very least the connection-request packet must have got through, but ... If you have strace or ktrace or similar on the Solaris machine, tracing psql's kernel calls might be revealing. What you want to watch for is whether psql is exiting with the connection still open, or whether it receives an EOF indication and then quits. BTW, what authorization mode are you trying to use for this connection? You might experiment with some different ones to see if the behavior changes. Also, what about turning SSL on or off? regards, tom lane