Received: from mx1.sabre.com (mx1.sabre.com [199.100.49.110]) by hub.org (8.9.3/8.9.3) with ESMTP id PAA74203 for ; Mon, 24 May 1999 15:47:13 -0400 (EDT) (envelope-from swheeler@sabre.com) Received: (from mailer@localhost) by mx1.sabre.com (8.9.3/8.9.0) id OAA01912 for ; Mon, 24 May 1999 14:46:41 -0500 (CDT) Received: from (pop3.sabre.com [144.9.112.62]) by mx1.sabre.com via smap (V2.1) id xma001689; Mon, 24 May 99 14:46:05 -0500 Received: from sabre.com ([172.29.63.42]) by pop3.sabre.com (Netscape Messaging Server 3.6) with ESMTP id AAA30F6 for ; Mon, 24 May 1999 14:46:04 -0500 Message-ID: <3749AB63.44E3463F@sabre.com> Date: Mon, 24 May 1999 14:41:23 -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: pgsql-sql@hub.org Subject: Fatal process interaction References: <199905140300.XAA39763@hub.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit The situation: In xterm #1: psql running, connected to database pssdb, executing an SQL select statement. In xterm #2: A shell script is run that pipes another select statement throug psql. When the select statement in xterm #2 completes, the select statement being executed in xterm #1 aborts and the following error message is output: NOTICE: Message from PostgreSQL backend: The Postmaster has informed me that some other backend died abnormally and possibly corrupted shared memory. I have rolled back the current transaction and am going to terminate your database system connection and exit. Please reconnect to the database system and repeat your query. pqReadData() -- backend closed the channel unexpectedly. This probably means the backend terminated abnormally before or while processing the request. We have lost the connection to the backend, so further processing is impossible. Terminating. This problem is very repeatable and does not seem to depend on which UID is running which session. They can both be postgres, or me (smw) or one of each. The one common factor appears to be that psql is involved in both. If psql is run in interactive mode in both windows, then \q is issued in one of the windows, both psql sessions will terminate. Any ideas? -- Steven M. Wheeler UNIX Engineering The SABRE Group (918) 292-4119 (918) 292-4165 FAX