Ticket #1163 (closed defect: fixed)
move SQL-exposed functions out of libpgcommon
|Reported by:||bnordgren||Owned by:||pramsey|
In general, it seems that anything having a need to be directly accessible to SQL should not be in libpgcommon, but rather in postgis or raster. Putting it in libpgcommon seems to be causing an issue for Windows.
Attached patch cleans out libpgcommon. Apply against r7757