[postgis-tickets] [PostGIS] #5332: Override proj_log_func to stop proj errors leaking out to PgSQL logs

[PostGIS]

#5332: Override proj_log_func to stop proj errors leaking out to PgSQL logs
--------------------------+---------------------------
  Reporter:  pramsey      |      Owner:  pramsey
      Type:  enhancement  |     Status:  assigned
  Priority:  medium       |  Milestone:  PostGIS 3.4.0
 Component:  postgis      |    Version:  3.3.x
Resolution:               |   Keywords:
--------------------------+---------------------------
Comment (by Paul Ramsey <pramsey@…>):

 In [changeset:"404b11de50a4715123c2f203353f192f927c1bee/git" 404b11d/git]:
 {{{#!CommitTicketReference repository="git"
 revision="404b11de50a4715123c2f203353f192f927c1bee"
 When libproj throws at error, don't just write the
 message to stderr. Catch it and put it into the
 PgSQL log at a DEBUG level.
 We check all return values and return codes when
 calling into the proj API, so the extra error messages
 don't really help us.
 This is in response to our calls to proj_create()
 dumping messages into stderr, which confuses operators.
 Our projection code has to try a bunch of possible
 strings to instantiate projection objects, some of
 which fail (generating a message) and then we fall
 back to the next string. The proj "errors" are not
 errors from our pov, so we catch them and send them
 along at much lower priority.
 References #5332
 }}}
-- 
Ticket URL: <https://trac.osgeo.org/postgis/ticket/5332#comment:2>
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.