From: Tom Lane <tgl@sss.pgh.pa.us>
To: stimits@comcast.net
Cc: postgresql <pgsql-interfaces@postgresql.org>
Subject: Re: more on undefined reference to 'pg_detoast_datum'
Date: Mon, 13 Oct 2003 10:42:40 -0400
Message-ID: <14311.1066056160@sss.pgh.pa.us> (raw)
In-Reply-To: <3F8A64DF.1080008@comcast.net>
References: <3F886324.8020707@comcast.net>
<558.1065936082@sss.pgh.pa.us>
<3F8A64DF.1080008@comcast.net>
"D. Stimits" <stimits@comcast.net> writes:
> ... My question is, where the heck is
> CurrentMemoryContext and MemoryContextAlloc provided as an
> implementation which I can link with?
They're inside the backend, and you don't --- you are not trying to
build a standalone executable with no unresolved symbols, but a shared
library that can be successfully loaded into the backend. It's okay
for such a library to have unresolved references to symbols that will be
resolved at load time.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: tgl@sss.pgh.pa.us, stimits@comcast.net
Subject: Re: more on undefined reference to 'pg_detoast_datum'
In-Reply-To: <14311.1066056160@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox