Return-Path: aoki
Received: by postgres.Berkeley.EDU (5.61/1.29)
	id AA03849; Thu, 13 May 93 11:43:46 -0700
Message-Id: <9305131843.AA03849@postgres.Berkeley.EDU>
From: aoki@postgres.berkeley.edu (Paul M. Aoki)
Subject: Re: VARLENATT
To: postgres@postgres.berkeley.edu
Sender: pg_adm@postgres.berkeley.edu
In-Reply-To: Your message of Thu, 13 May 93 17:20:26 MESZ 
	     <9305131521.AA01596@postgres.Berkeley.EDU> 
Date: Thu, 13 May 93 11:43:45 -0700
Sender: aoki@postgres.Berkeley.EDU
X-Mts: smtp

ok.  first, the reason you get all of those "ufp..." errors is that 
you are marking your functions with "trusted=f".  now..

Wolf Guddat <guddat@faps.uni-erlangen.de> writes:
>  both routines doing nothing else than returning NULL 

this is the problem.  ok, more error-checking should be done so 
that the untrusted function process handles null pointers more
correctly.. but in general the in/out functions should return 
valid pointers or raise an exception.  (hmm... i wonder how well 
this piece of code works with trusted=t..)

the unhelpful error messages are due to looking at errno when
the error is user-level (wrong number of bytes received) instead 
of system-call level.
--
  Paul M. Aoki  |  CS Div., Dept. of EECS, UCB  |  aoki@postgres.Berkeley.EDU
                |  Berkeley, CA 94720           |  ...!uunet!ucbvax!aoki
