> > Which brings me to the question - would it be reasonable to
> create a
> > .DEF file listing which symbols are exported from the
> postgres binary
> > to addon modules?
>
> No, I'd not think this is a good idea. Unlike libpq, there's
> no clear demarcation of an intended API, and no real
"Magnus Hagander" <[EMAIL PROTECTED]> writes:
> Which brings me to the question - would it be reasonable to create a
> .DEF file listing which symbols are exported from the postgres binary to
> addon modules?
No, I'd not think this is a good idea. Unlike libpq, there's no clear
demarcation of an
On Sat, Apr 29, 2006 at 10:56:20AM +0200, Magnus Hagander wrote:
> While working on the VC++ build, I initially (accidentally) built
> postgres.exe witohut exporting all symbols (because VC++ doesn't have a
> builtin functionality to do export-all). When enabling it to export all,
> I noticed the b
While working on the VC++ build, I initially (accidentally) built
postgres.exe witohut exporting all symbols (because VC++ doesn't have a
builtin functionality to do export-all). When enabling it to export all,
I noticed the binary increased more than 30% in size, and the linker
time increased arou
