Changes between Initial Version and Version 1 of Ticket #3238, comment 5
- Timestamp:
- 08/16/15 14:27:36 (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #3238, comment 5
initial v1 3 3 What I am noticing here, though its postgis_lib_version() triggering the issue, it doesn't happen if I call postgis_lib_version() directly. 4 4 5 So as far as I can reckon, the postgis_lib_version() is maybe trying to flip back to geos (it's default state), and it can't do that when it's running with postgis_full_version();5 So as far as I can reckon, the postgis_lib_version() is maybe trying to flip back to geos (it's default state), and it can't do that when it's running within postgis_full_version(); because it's illegal for a subprocess to do that in within a transaction. 6 6 7 7 Anyrate, all works fine (aside from that annoying topology message), when I flip back to geos backend.