Received: from localhost.localdomain (postgresql.org [64.49.215.8])
	by localhost (Postfix) with ESMTP id 6829A476B5C
	for <pgsql-sql@postgresql.org>; Thu, 20 Jun 2002 09:32:23 -0400 (EDT)
Received: from sss.pgh.pa.us (unknown [192.204.191.242])
	by postgresql.org (Postfix) with ESMTP id 958F84765A0
	for <pgsql-sql@postgresql.org>; Thu, 20 Jun 2002 09:28:48 -0400 (EDT)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id g5KDSN111462;
	Thu, 20 Jun 2002 09:28:24 -0400 (EDT)
To: Christoph Haller <ch@rodos.fzk.de>
Cc: pgsql-sql@postgresql.org
Subject: Re: psql -E <dbname> Floating exception (coredump) 
In-reply-to: <200206200838.KAA25851@rodos> 
References: <200206200838.KAA25851@rodos>
Comments: In-reply-to Christoph Haller <ch@rodos.fzk.de>
	message dated "Thu, 20 Jun 2002 10:38:53 +0700"
Date: Thu, 20 Jun 2002 09:28:23 -0400
Message-ID: <11459.1024579703@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Archive-Number: 200206/271
X-Sequence-Number: 8236

Christoph Haller <ch@rodos.fzk.de> writes:
> NOTICE:  current transaction is aborted, queries ignored until end of transaction block
> Floating exception(coredump)
> I doubt this is intended. 

I don't see a crash with current sources.  I believe this was fixed
a couple months ago, see
http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/psql/print.c

			regards, tom lane