[postgis-tickets] [PostGIS] #5076: Extension install with pgaudit in place generates log explosion

[PostGIS]

#5076: Extension install with pgaudit in place generates log explosion
----------------------+---------------------------
  Reporter:  pramsey  |      Owner:  pramsey
      Type:  defect   |     Status:  new
  Priority:  medium   |  Milestone:  PostGIS 3.3.0
 Component:  postgis  |    Version:  3.2.x
Resolution:           |   Keywords:
----------------------+---------------------------

Comment (by pramsey):

 I see two possible approaches,

 * Test for the presence of a non-none pgaudit setting at the start of
 extension script and just error out with a useful message, like "set
 pgaudit.log to none!"
 * Automatically flip the pgaudit mode to none at the top of the script if
 it's not already none, and then flip it back to its real value at the end.
 This seems magical and potentially adds complexity to no great benefit.
 Example implementation
 https://gist.github.com/pramsey/4c65bc65b753efed52955be6bd60e507

-- 
Ticket URL: <https://trac.osgeo.org/postgis/ticket/5076#comment:1>
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.