[postgis-tickets] [PostGIS] #3515: tiger_data not being backed up

[PostGIS]

#3515: tiger_data not being backed up
----------------------------+---------------------------
 Reporter:  robe            |      Owner:  robe
     Type:  defect          |     Status:  new
 Priority:  blocker         |  Milestone:  PostGIS 2.2.3
Component:  tiger geocoder  |    Version:  2.2.x
 Keywords:                  |
----------------------------+---------------------------
 Just discovered that tiger_data is not being backed up as part of a
 regular backup.  I thought the issue was because I specifically exclude it
 cause its the same and takes up so much space.

 Then I did a regular old backup and to my horror, the tiger_data schema
 did not get backed up.

 To fix I had to:


 {{{
 ALTER EXTENSION postgis_tiger_gecoder DROP SCHEMA tiger_data;
 }}}


 I think this started happening when I started automatically creating the
 tiger_data schema as part of create extension.  I never thought that if
 tiger_data is part of the extension it would mean the tables would be as
 well and not come backup.

 This personally seems like a bug to me, so I should probably verify
 upstream to be sure.

--
Ticket URL: <https://trac.osgeo.org/postgis/ticket/3515>
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.