Return-Path: owner-postman 
Delivery-Date: Thu, 07 Apr 94 14:35:01 -0700
Return-Path: owner-postman
Received: from localhost (localhost [127.0.0.1]) by nobozo.CS.Berkeley.EDU (8.6.4/8.6.3) with SMTP id KAA19237 for postgres-redist; Thu, 7 Apr 1994 10:34:27 -0700
Resent-From: POSTGRES mailing list <postman@postgres.Berkeley.EDU>
Resent-Message-Id: <199404071734.KAA19237@nobozo.CS.Berkeley.EDU>
Sender: owner-postman@postgres.Berkeley.EDU
X-Return-Path: owner-postman
Received: from faerie.CS.Berkeley.EDU (faerie.CS.Berkeley.EDU [128.32.149.14]) by nobozo.CS.Berkeley.EDU (8.6.4/8.6.3) with ESMTP id KAA19228 for <postgres@postgres.Berkeley.EDU>; Thu, 7 Apr 1994 10:34:26 -0700
Received: from localhost (localhost [127.0.0.1]) by faerie.CS.Berkeley.EDU (8.6.4/8.1B) with SMTP id KAA10327; Thu, 7 Apr 1994 10:33:56 -0700
Message-Id: <199404071733.KAA10327@faerie.CS.Berkeley.EDU>
X-Authentication-Warning: faerie.CS.Berkeley.EDU: Host localhost didn't use HELO protocol
From: aoki@postgres.Berkeley.EDU (Paul M. Aoki)
To: "David Alan Nelson" <D.A.Nelson@newcastle.ac.uk>
Cc: postgres@postgres.Berkeley.EDU
Subject: Re: regression test failed 
Reply-To: aoki@postgres.Berkeley.EDU (Paul M. Aoki)
In-reply-to: Your message of Thu, 7 Apr 1994 14:40:27 +0100 (BST) 
	     <AA19248.9404071340@swinhoe.ncl.ac.uk> 
Date: Thu, 07 Apr 94 10:33:56 -0700
X-Sender: aoki@postgres.Berkeley.EDU
Resent-To: postgres-redist@postgres.Berkeley.EDU
X-Mts: smtp
Resent-Date: Thu, 07 Apr 94 10:34:27 -0700
Resent-XMts: smtp

"David Alan Nelson" <D.A.Nelson@newcastle.ac.uk> writes:
> > Query sent to backend is "replace temp (stringu1 = reverse_c16(o.stringu1))
     from o in onek     where o.stringu1 = "JBAAAA" and 	  o.stringu1 = 
temp.stringu1 "
> > WARN:Feb 21 12:04:28:Load of file /sd2g/prj/postgres/src/regress/regress/ob
j/../obj/regress.o failed: link failed!
> So did I.  Anybody care to explain why this happens.

this can happen for any number of reasons, generally having to
do with your environment.  one is running out of link space in 
/tmp.  the more common one is broken file permissions (the 
postgres user must be able to access that file, meaning you 
should be able to "su postgres" (or whoever the postmaster is 
running as), cd to that directory and (e.g.) "cat" the .o file.

the former problem cannot occur in postgres 4.2 because we no 
longer use "ld -A" style dynamic linking.
--
  Paul M. Aoki  |  CS Div., Dept. of EECS, UCB  |  aoki@postgres.Berkeley.EDU
                |  Berkeley, CA 94720           |  ...!uunet!ucbvax!aoki