From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Preston A(dot) Elder" <prez(at)neuromancy(dot)net> |
Cc: | pgsql-interfaces(at)postgresql(dot)org |
Subject: | Re: Portable interfaces ... |
Date: | 2004-03-23 05:05:32 |
Message-ID: | 15657.1080018332@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces |
"Preston A. Elder" <prez(at)neuromancy(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Preston A. Elder | 2004-03-23 05:38:38 | Re: Portable interfaces ... |
Previous Message | Preston A. Elder | 2004-03-23 03:22:02 | Portable interfaces ... |