Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2])
	by hub.org (8.9.3/8.9.3) with ESMTP id AAA64379
	for <pgsql-interfaces@postgreSQL.org>;
	Thu, 18 Nov 1999 00:46: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 AAA27688;
	Thu, 18 Nov 1999 00:45:47 -0500 (EST)
To: Rob Brown-Bayliss <rob@ZOOstation.cc>
cc: Postgres Mailing list <pgsql-interfaces@postgreSQL.org>
Subject: Re: [INTERFACES] PQfinish kills my app 
In-reply-to: Your message of Thu, 18 Nov 1999 18:08:48 +1300
	<383389E0.A139756F@ZOOstation.cc>
Date: Thu, 18 Nov 1999 00:45:47 -0500
Message-ID: <27686.942903947@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

Rob Brown-Bayliss <rob@ZOOstation.cc> writes:
> So I don't understand why it dies on PQfinish one way but not the
> other.  But, if I do not call exit_nicely (ie: just end without
> PQfinish) ir dies on option -v but works for option -a

Kinda sounds like you might be calling PQfinish more than once on
the same connection object.  That's a no-no.

> PS: By die I mean seagfault, I traced wit with gdb to the PQfinish
> function.  As I am new to the GNU tools (and fairly new to C) I am not
> sure whats going on.  I could post the code, but was not sure about the
> list rules, it's 8 k long.

People have posted much larger messages than 8k with less reason.
If the multiple-calls idea doesn't pan out, let's see it...

			regards, tom lane