[postgis-tickets] [PostGIS] #4302: ST_MemSize for geography

[PostGIS]

#4302: ST_MemSize for geography
-----------------------+---------------------------
  Reporter:  ezimanyi  |      Owner:  pramsey
      Type:  defect    |     Status:  closed
  Priority:  medium    |  Milestone:  PostGIS 2.5.2
 Component:  postgis   |    Version:  2.4.x
Resolution:  wontfix   |   Keywords:
-----------------------+---------------------------
Changes (by robe):

 * status:  reopened => closed
 * resolution:   => wontfix


Comment:

 I'm closing this as a wontfix.  Of all the functions we could possibly
 choose to support for geography, ST_Memsize is up there in the dumbest
 category.

 That said geography is a second class citizen because it came second and
 we purposely DID not just wrap it in geometry because

 a) 4326 would then be slow in geometry and often times people just don't
 care planar even  for 4326 is often good enough

 b) We had toyed with autocasts so that geography would just autocast
 itself to use geometry functions where it could. We took that out because
 it caused too many ambiguous function this and that when people toyed with
 using 'POLYGON(....)'  and also when it did autocast, it was ahocking
 surprise in many cases.

 We still have a bit of a shocking surprise that geometry autocasts to
 geography as in the case with the stupid hack people use of
 ST_Distance(geometry, true)

 c) Adding a native geography function for every geometry would balloon our
 list of function 300 more and would be a huge pain to maintain.

-- 
Ticket URL: <https://trac.osgeo.org/postgis/ticket/4302#comment:8>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.