Reinstall PostgreSQL extensions on upgrade, drop pg_catalog.pg_trgm

Description

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 use pg_catalog.gin_trgm_ops. RMB automatically recreates gin indexes using public.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

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Checklist

hide

TestRail: Results

Activity

Show:
Done

Details

Assignee

Reporter

Priority

Story Points

Sprint

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
TestRail: Cases
TestRail: Runs