Choosing PostgreSQL extensions for an Oracle migration

The key question

An extension available on a developer laptop is not automatically available on the eventual managed service. Platform selection and the extension list therefore need to be validated together.

What to inventory

• List required capabilities separately from candidate extensions.
• Record source version, target version and provider support.
• Capture installation privileges, upgrade path and dependencies.

Design the target deliberately

Start with the business requirement. Then decide whether PostgreSQL core features, application code or an extension are the best fit. For every selected extension, document how it will be monitored, upgraded and replaced if the platform changes.

A concrete validation step

SELECT name, default_version, installed_version
FROM pg_available_extensions
ORDER BY name;

Evidence required before sign-off

• Verify availability on the exact target service.
• Install and upgrade in a separate test environment.
• Test backup and restore with all required extensions.
• Detect missing or mismatched extension versions during deployment.