Opened 3 years ago

Closed 3 years ago

#3515 closed defect (fixed)

tiger_data not being backed up

Reported by: robe Owned by: robe
Priority: blocker Milestone: PostGIS 2.2.3
Component: tiger geocoder Version: 2.2.x
Keywords: Cc:

Description

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.

Change History (3)

comment:1 Changed 3 years ago by robe

Reported upstream. Hasn't always been this way, so I don't feel quite so negligent missing this issue. I'm still going to make this change since I never actually intended tiger_data schema to be considered part of the extension and was created just for convenience.

http://www.postgresql.org/message-id/flat/000601d18714$ea4aee90$bee0cbb0$@pcorp.us#000601d18714$ea4aee90$bee0cbb0$@pcorp.us

comment:2 Changed 3 years ago by robe

In 15026:

perl as found by configure is not used in tiger, sfcgal, or address_standardizer extensions
references #3602 for PostGIS 2.3 (trunk)
tiger_data not being backed up and add upgrade test
references #3515 for PostGIS 2.3 (trunk)

comment:3 Changed 3 years ago by robe

Resolution: fixed
Status: newclosed

In 15027:

perl as found by configure is not used in tiger, sfcgal, or address_standardizer extensions
closes #3602 for PostGIS 2.2
tiger_data not being backed up and add upgrade test
closes #3515 for PostGIS 2.2

Note: See TracTickets for help on using tickets.