Opened 11 years ago

Closed 11 years ago

Last modified 3 years ago

#267 closed enhancement (wontfix)

Use of GUC to determine default (sphere/spheroid) calculation for geography

Reported by: robe Owned by: pramsey
Priority: low Milestone: PostGIS Fund Me
Component: postgis Version: master
Keywords: Cc: mloskot


I think we had discussed the use of defining GUCs at least for some other PostGIS thing since PostgreSQL allows modules to load custom GUCs. Forget what we were thinking for before to use it for, and forget why we decided against it.

It would seem that that would be the ideal way of allowing people to control which measurement behavior they would prefer for the ST_Area, ST_Distance etc. functions and we could default this behavior to sphere as we are doing currently.

This we may need to table till postgis 2.0.

Change History (5)

comment:1 Changed 11 years ago by mloskot

Cc: mloskot added

comment:2 Changed 11 years ago by pramsey

Milestone: postgis 2.0.0postgis 1.5.0

We decided against it because the GUC can't be set using the "SET" syntax until after the dynamic module is loaded, and that doesn't happen until the first function is called. Could be worked around by providing the functionality via a set_blah() function instead of the SET syntax. Need to decide if we want this for real. I'm indifferent, except insofar as it makes things a little more complex to document.

comment:3 Changed 11 years ago by pramsey

Resolution: wontfix
Status: newclosed

I think with function signatures we are fine as things are, I'm closing this one out until someone comes with their hair on fire needing it.

comment:4 Changed 8 years ago by strk

Milestone: PostGIS 1.5.0PostGIS Future

See #1393 for a generic ticket about GUC

comment:5 Changed 3 years ago by robe

Milestone: PostGIS FuturePostGIS Fund Me

Milestone renamed

Note: See TracTickets for help on using tickets.