From: Tom Lane <tgl@sss.pgh.pa.us>
To: Preston A. Elder <prez@neuromancy.net>
Cc: pgsql-interfaces@postgresql.org
Subject: Re: Portable interfaces ...
Date: Tue, 23 Mar 2004 00:05:32 -0500
Message-ID: <15657.1080018332@sss.pgh.pa.us> (raw)
In-Reply-To: <1080012121.10179.56.camel@temple.srealm.net.au>
References: <1080012121.10179.56.camel@temple.srealm.net.au>
"Preston A. Elder" <prez@neuromancy.net> writes:
> I wanted to know exactly which header files I can use portably.
pg_type.h is part of the "server-side" include tree. When installing
from original sources, it is installed only if you type "make
install-all-headers". When dealing with a Linux distribution's
packaging, it's completely at the whim of the packager whether it will
be installed at all, and if so where.
Sorry the news isn't better :-(. My advice would actually be to copy
the #define's you need for type OIDs into a header in your own sources.
We do not make a practice of changing OIDs for built-in objects, so I
think your risk in that direction is really lower than your risk from
trying to #include pg_type.h on various random distributions.
I don't have a comparably simple answer for your character encoding
issue, but again I fear that relying on PG's internal facilities would
be a bad idea for you.
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, prez@neuromancy.net
Subject: Re: Portable interfaces ...
In-Reply-To: <15657.1080018332@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