X-Original-To: pgsql-interfaces-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id 81154D1B4FC for ; Sat, 11 Oct 2003 20:08:24 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 23152-04 for ; Sat, 11 Oct 2003 17:07:45 -0300 (ADT) Received: from sccrmhc13.comcast.net (sccrmhc13.comcast.net [204.127.202.64]) by svr1.postgresql.org (Postfix) with ESMTP id 6968ED1B516 for ; Sat, 11 Oct 2003 17:07:35 -0300 (ADT) Received: from comcast.net (12-253-72-16.client.attbi.com[12.253.72.16]) by comcast.net (sccrmhc13) with SMTP id <20031011200747016002qim7e> (Authid: stimits); Sat, 11 Oct 2003 20:07:48 +0000 Message-ID: <3F886324.8020707@comcast.net> Date: Sat, 11 Oct 2003 14:08:04 -0600 From: "D. Stimits" Reply-To: stimits@comcast.net User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2b) Gecko/20021018 X-Accept-Language: en-us, en MIME-Version: 1.0 To: postgresql Subject: more on undefined reference to 'pg_detoast_datum' and libpq Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200310/24 X-Sequence-Number: 4513 Apparently in PosgreSQL 7.2.3 (the Redhat 7.3 version, which has some patching involved), pg_detoast_datum is defined in fmgr backend code, but this function is not defined anywhere in any library, especially not libpq. It is the necessity to use fmgr.h functions that brings about the need to have pg_detoast_datum. The V1 interface itself requires fmgr.h, this is where PG_FUNCTION_INFO_V1 is declared, along with other V1 macros. My guess is that pg_detoast_datum should be in a library somewhere, but manually compiling PostgreSQL 7.2.3 source with unstripped libraries shows that no dynamic library produced from the source build contains the necessary functions. There does not appear to be any libfmgr.so (of any version), unless there is some configure option I am missing. How do I get around this without using non-Redhat packages and without forcing users to install another version of PostgreSQL? At this point it looks like there is no choice but to use the V0 interface to libpq and develop separate projects for other versions of linux PostgreSQL that have more recent versions. D. Stimits