Return-Path: aoki
Received: by postgres.Berkeley.EDU (5.61/1.29)
	id AA15441; Wed, 11 Aug 93 12:11:25 -0700
Message-Id: <9308111911.AA15441@postgres.Berkeley.EDU>
From: aoki@postgres.Berkeley.EDU (Paul M. Aoki)
Subject: Re: LIBPQ error handling...
To: postgres@postgres.berkeley.edu
Sender: pg_adm@postgres.berkeley.edu
In-Reply-To: Your message of Wed, 11 Aug 93 11:37:21 -0700 
	     <9308111837.AA15101@postgres.Berkeley.EDU> 
Date: Wed, 11 Aug 93 12:19:25 -0700
Sender: aoki@postgres.Berkeley.EDU
X-Mts: smtp

witr@rwwa.COM writes:
> Is it a feature of all Postgres 4.0.1 ports that errors detected in a
> LIBPQ query cause the error/exception handling stuff to tight loop and
> eventually core?  Or is it just a feature of my port?

(i hate answering questions about old ports ..)

don't know if this causes your problem, but i think there are some 
places in the 4.0.1 PQexec() where it tries to return a string in a 
char array that is an automatic variable :-P  at least, this also 
caused rik turnbull's hpux port to do the same thing..

i think if you make PQcommand a static variable things work better.
--
  Paul M. Aoki  |  CS Div., Dept. of EECS, UCB  |  aoki@postgres.Berkeley.EDU
                |  Berkeley, CA 94720           |  ...!uunet!ucbvax!aoki