Revision 14443
Added by Aaron Marcuse-Kubitza over 10 years ago
| make_analytical_db | ||
|---|---|---|
| 20 | 20 |
SELECT geoscrub_input_view_modify(); |
| 21 | 21 |
|
| 22 | 22 |
SELECT taxon_trait_view_modify(); |
| 23 |
SELECT analytical_stem_view_modify();
|
|
| 23 |
SELECT viewFullOccurrence_individual_view_modify();
|
|
| 24 | 24 |
SELECT provider_count_view_modify(); |
| 25 | 25 |
EOF |
| 26 | 26 |
) || exit |
Also available in: Unified diff
bin/make_analytical_db: materialize viewFullOccurrence_individual_view instead of analytical_stem_view because analytical_stem_view is now generatable via a simple join onto viewFullOccurrence_individual_view. this avoids running into potential disk space constraints when materializing and backing up both tables (~50 GB/table * 2 tables * 2 copies (incl. the backup) = 200 GB, which is very close to the available disk space).