Skip site navigation (1) Skip section navigation (2)

Exports from postgres

From: "Magnus Hagander" <mha(at)sollentuna(dot)net>
To: <pgsql-hackers(at)postgresql(dot)org>
Subject: Exports from postgres
Date: 2006-04-29 08:56:20
Message-ID: 6BCB9D8A16AC4241919521715F4D8BCEA0F945@algol.sollentuna.se (view raw or flat)
Thread:
Lists: pgsql-hackers
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 around 500%. (The reason the function is not in vc++ is
that you're really not supposed to do full-exports from EXEs and
DLLs...)

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? Sort of the same way libpq does it, though of course with
a much more extensive list of functions. I have a feeling this might be
both more work than wanted, and something contrary to some piece of
design, but I'm throwing the question out to get some expert comments on
it. 

//Magnus

Responses

pgsql-hackers by date

Next:From: Martijn van OosterhoutDate: 2006-04-29 10:39:04
Subject: Re: Exports from postgres
Previous:From: Andrew DunstanDate: 2006-04-29 06:10:19
Subject: Re: for statement, adding a STEP clause?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group