[PORTS] Compiling table_log and other C-functions on the windows port of 8.3

This is a multi-part message in MIME format.

--Boundary_(ID_2oFY8QDrAvgg4gE4BlA2Vw)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Content-disposition: inline

Can the C-functions oftable_log (http://pgfoundry.org/projects/tablelog/) and/or the exampleC-functions in the postgresql docs be compiled for the windows port ofpg 8.3 using Visual C++ (preferentially VC++ 2008) with the header and library files supplied withthe binary installer? If so, which Visual C++ compiler/linkersettings/switches are needed to produce a dll that can be successfullyloaded by postgresql? It would be good to have this information in thesection on compiler settings for compilation of C-functions in docs 34.9, like there is for othercompilers in 34.9.6.

Thanks,
KP

--Boundary_(ID_2oFY8QDrAvgg4gE4BlA2Vw)
Content-type: text/html; charset=us-ascii
Content-transfer-encoding: 7BIT
Content-disposition: inline

<font face="'PrimaSans BT,Verdana,sans-serif'">Can the C-functions oftable_log (http://pgfoundry.org/projects/tablelog/) and/or the exampleC-functions in the postgresql docs be compiled for the windows port ofpg 8.3 using Visual C++ (preferentially VC++ 2008) with the header and library files supplied withthe binary installer? If so, which Visual C++ compiler/linkersettings/switches are needed to produce a dll that can be successfullyloaded by postgresql? It would be good to have this information in thesection on compiler settings for compilation of C-functions in docs 34.9, like there is for othercompilers in 34.9.6.<br><br>Thanks,<br>KP</font>

--Boundary_(ID_2oFY8QDrAvgg4gE4BlA2Vw)--