1. Describe issue impact on business Database maintenance (VACUUM ANALYZE) fails. Migration from PostgreSQL 12 to 16 fails. 2. What institutions are affected? (field “Affected Institutions” in Jira to be populated) GBV Index Data (Lesley) 3. What is the workaround if exists? None. There's no other way than fixing the function in the database. 4. What areas will be impacted by fix (i.e. what areas need to be retested) It's a database index for requests, however, only database sysops can test whether the fix has been applied, the fix is non-testable in UI/in APIs. 5. Brief explanation of technical implementation and the level of effort (in workdays) and technical risk (low/medium/high) Revert CIRCSTORE-377. Then the database function will have the schema again. It will be reverted to the function code as it was in Poppy and before. Less than one workday effort. Low technical risk. 6. Brief explanation of testing required and level of effort (in workdays). Provide test plan agreed with by QA Manager and PO. Known to work because we revert to code we have had been using in Orchid and Poppy. Existing automated tests are sufficient to ensure that there are no regressions. Testing effort is less than a workday. 7. What is the roll back plan in case the fix does not work? If it causes major regressions we will create a new CSP with the revert of the revert.