*** This version of Confluence is for testing only and contains a copy of content from June 29th 2026. No changes will be preserved. ***
-
Created by
Sharon Helen Markus, last updated on Aug 06, 2025
1 minute read
There is an ongoing effort to reduce the number of tables in the Metadb reporting database that are synchronized with FOLIO for updates to the data. This is done to improve the performance of Metadb overall. Also, some tables may be excluded to address problems impacting FOLIO applications.
| Date Excluded | Schema | Table | Size | Reason to Exclude |
|---|---|---|---|---|
| 8/5/25 | folio_inventory | instance_subject_source | This is being excluded temporarily as a fix for the lack of a primary key in the Data Import app development that causes replica identity errors while synchronizing | |
| 8/5/25 | folio_inventory | instance_subject_type | This is being excluded temporarily as a fix for the lack of a primary key in the Data Import app development that causes replica identity errors while synchronizing | |
| folio_source_record_manager | journal_records | 372 GB | ||
| folio_source_record_manager | all tables? | Do we need to synchronize any of these tables? | ||
| folio_audit | circulation_logs | 65 GB | ||
| folio_configuration | all tables? | Do we need to synchronize any of these tables? | ||
| folio_copycat | all tables? | Do we need to synchronize any of these tables? | ||
| old_records_tracking |