Done
Details
Assignee
Julian LadischJulian LadischReporter
Julian LadischJulian LadischLabels
Priority
P3Story Points
0.5Sprint
NoneDevelopment Team
Core: PlatformFix versions
Release
Q2 2020Affected Institution
TAMUTestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee
Julian Ladisch
Julian LadischReporter
Julian Ladisch
Julian LadischLabels
Priority
Story Points
0.5
Sprint
None
Development Team
Core: Platform
Fix versions
Release
Q2 2020
Affected Institution
TAMU
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created July 7, 2020 at 2:32 PM
Updated July 17, 2020 at 10:21 AM
Resolved July 8, 2020 at 3:38 PM
As an SysOp I want to run the upgrade on a system that is based on a freshly installed backup. The backup may miss the PostgreSQL extensions that reside in public schema. Example:
To make the life of SysOps easier be forgiving and reinstall all PostgreSQL extensions on upgrade.
pg_trgm may have incorrectly been created in
pg_catalog
schema, see bug report in . Drop pg_trgm if it is in a wrong schema.Note: A PostgreSQL extension can be loaded into one schema only. If there are several schemata that want to make use of the features that the extension provides they need to share the loaded extensions of one schema. In FOLIO the public schema is used for this purpose. Using extension features requires access to the public schema.
Dropping pg_trgm in
pg_catalog
automatically drops all indexes that usepg_catalog.gin_trgm_ops
. RMB automatically recreates gin indexes usingpublic.gin_trgm_ops
: https://github.com/folio-org/raml-module-builder/blob/v30.0.0/domain-models-runtime/src/main/resources/templates/db_scripts/indexes.ftl#L48