Opened 7 years ago
Closed 7 years ago
#3515 closed defect (fixed)
tiger_data not being backed up
|Reported by:||robe||Owned by:||robe|
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 by , 7 years ago
comment:2 by , 7 years ago
comment:3 by , 7 years ago
|Status:||new → closed|
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.