Received: from mx1.sabre.com (mx1.sabre.com [199.100.49.110]) by hub.org (8.9.3/8.9.3) with ESMTP id OAA51836 for ; Tue, 25 May 1999 14:54:02 -0400 (EDT) (envelope-from swheeler@sabre.com) Received: (from mailer@localhost) by mx1.sabre.com (8.9.3/8.9.3) id NAA00133 for ; Tue, 25 May 1999 13:53:30 -0500 (CDT) Received: from (pop3.sabre.com [144.9.112.62]) by mx1.sabre.com via smap (V2.1) id xma029950; Tue, 25 May 99 13:52:34 -0500 Received: from sabre.com ([172.29.63.42]) by pop3.sabre.com (Netscape Messaging Server 3.6) with ESMTP id AAA27AD; Tue, 25 May 1999 13:52:26 -0500 Message-ID: <374AF061.F2F74F44@sabre.com> Date: Tue, 25 May 1999 13:48:01 -0500 From: "Steven M. Wheeler" Organization: The SABRE Group, UNIX Engineering X-Mailer: Mozilla 4.51 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: Tom Lane CC: pgsql-sql@hub.org Subject: Re: [SQL] Fatal process interaction References: <1722.927592436@sss.pgh.pa.us> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit More info. Motivated by your remark about SysV semaphores, I upgraded the kernel to 2.0.36 and the problem appears to have gone away. -- Steven M. Wheeler UNIX Engineering The SABRE Group (918) 292-4119 (918) 292-4165 FAX Tom Lane wrote: > "Steven M. Wheeler" writes: > > If psql is run in interactive mode in both windows, then \q is issued > > in one of the windows, both psql sessions will terminate. > > Wow, that's pretty bizarre. What platform are you on? I think the FAQ > mentions that problems like this have been seen on systems where SysV > semaphore support wasn't configured or didn't work right ... > > regards, tom lane