Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154])
	by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f27Gtrx02696;
	Wed, 7 Mar 2001 11:55:53 -0500 (EST)
	(envelope-from tgl@sss.pgh.pa.us)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.11.1/8.11.1) with ESMTP id f27GtZ909812;
	Wed, 7 Mar 2001 11:55:35 -0500 (EST)
To: Hannu Krosing <hannu@tm.ee>
cc: Boulat Khakimov <boulat@inet-interactif.com>, pgsql-sql@postgresql.org,
	pgsql-docs@postgresql.org
Subject: Re: Extending PostgreSQL Using C 
In-reply-to: <3AA66671.7050306@tm.ee> 
References: <3AA40C7F.D56684AF@inet-interactif.com> <3AA66671.7050306@tm.ee>
Comments: In-reply-to Hannu Krosing <hannu@tm.ee>
	message dated "Wed, 07 Mar 2001 18:48:49 +0200"
Date: Wed, 07 Mar 2001 11:55:35 -0500
Message-ID: <9809.983984135@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Archive-Number: 200103/42
X-Sequence-Number: 473

Hannu Krosing <hannu@tm.ee> writes:
> Boulat Khakimov wrote:
>> ERROR:  Can't find function encrypt in file /[full path here]/encrypt.so 

> Can _postgres_ user read /[full path here]/encrypt.so ?

Presumably so.  If he were unable to load the .so file, he'd be getting
a different error message.  This message indicates that he got past the
load step, but dl_sym is unable to resolve the symbol "encrypt".

I asked about the symbol names shown by nm(1), but got no answer ...

			regards, tom lane