> Actually, the point of including c.h (plus postgres_ext.h) rather than
> postgres.h was to not have access to the backend internal stuff, so as to
> keep the separation clean. But it doesn't really matter to me. Also, on my
> system at least, there were no redundant includes. I actually went through
> each library call and put in exactly the includes the man page mentioned.
Yes, I suspected that was your purpose. I couldn't find any other areas
where c.h was used, so I figured I may as well make it standard, and if
we want to make it separate, we would have to do most of bin and
interfaces, and that would be a separate job.
-- Bruce Momjian | http://www.op.net/~candle pgman@candle.pha.pa.us | (610)
853-3000+ If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill,
Pennsylvania19026
