Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [206.210.65.6]) by hub.org (8.9.2/8.9.1) with ESMTP id LAA16177 for ; Sun, 21 Mar 1999 11:12:28 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id LAA07433; Sun, 21 Mar 1999 11:11:29 -0500 (EST) To: John Wright cc: pgsql-interfaces@postgreSQL.org Subject: Re: [INTERFACES] 6.4.2 psql/libpq not returning after error In-reply-to: Your message of Sun, 21 Mar 1999 13:58:57 +0000 <19990321135857.A690@aschamhs.demon.co.uk> Date: Sun, 21 Mar 1999 11:11:29 -0500 Message-ID: <7431.922032689@sss.pgh.pa.us> From: Tom Lane John Wright writes: > 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. > 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. It works for everyone else ... we could hardly have failed to notice such an obvious problem ;-) Are you perhaps trying to use a 6.4.x psql with a 6.3.x backend? (The older postmaster should've refused such a connection in the first place, however, so that doesn't seem likely.) It sounds like the backend is failing to fflush() out the last few characters of its response, but I'm at a loss to understand why that would be happening only for you and not all over the place. You might try attaching to the backend process and using gdb to see where it's sitting... regards, tom lane