Received: from tribal.internal (IDENT:smtp@aschamhs.demon.co.uk [158.152.127.149]) by hub.org (8.9.2/8.9.1) with ESMTP id IAA03515 for ; Sun, 21 Mar 1999 08:57:49 -0500 (EST) (envelope-from john@aschamhs.demon.co.uk) Received: from cosmo.internal (cosmo.internal [192.168.1.2]) by tribal.internal (Postfix) with ESMTP id BA2CBA11C; Sun, 21 Mar 1999 13:58:52 +0000 (GMT) Received: by cosmo.internal (Postfix, from userid 1000) id 9301260611; Sun, 21 Mar 1999 13:58:57 +0000 (GMT) Date: Sun, 21 Mar 1999 13:58:57 +0000 From: John Wright To: pgsql-interfaces@postgresql.org Subject: 6.4.2 psql/libpq not returning after error Message-ID: <19990321135857.A690@aschamhs.demon.co.uk> Mail-Followup-To: pgsql-interfaces@postgresql.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i Sender: john@aschamhs.demon.co.uk Hi, I've just installed postgres-6.4.2 after using 6.3.1 and I've noticed that when using psql and an error occurs psql locks up. Something like: SELECT 'XXX'::bool; will return an error using psql from 6.3.1 but will not return at all using the psql from 6.4.2. gdb shows that it is waiting on a select(). (gdb) bt #0 0x4010f4f3 in select () #1 0x40038c7c in pqWait () #2 0x40036f16 in PQgetResult () #3 0x400370ac in PQexec () #4 0x6698 in SendQuery (... The console running postmaster does display an error, though. My system is OpenBSD 2.5/i386. Any ideas? Known bug? Patch about? BFN, John -- Calculating line numbers... (interrupt to abort)