Andrew Chernow <ac@esilo.com> writes:
> If you are suggesting that libpqtypes should not access internal libpq,
> than this idea won't work. We can pull all the code out and hook in, as
> you suggested, but we had no plans of abstracting from internal libpq.
That's exactly what I'm strongly suggesting. If you need to include
libpq-int.h at all, then your library will be forever fragile, and could
very well end up classified as "don't ship this at all, it's too likely
to break".
regards, tom lane