All services are going offline.
You will not be able to downgrade back to Postgres {currentPgVersion}.
Your project will be offline for up to {durationEstimateHours} hour
{durationEstimateHours === 1 ? '' : 's'}
It is advised to upgrade at a time when there will be minimal impact for
your application.
{(data?.potential_breaking_changes ?? []).length > 0 && (
Breaking changes
Your project will be upgraded across major versions of Postgres. This
may involve breaking changes.
)}
{legacyAuthCustomRoles.length > 0 && (
Custom Postgres roles will not work automatically after upgrade
You must run a series of commands after upgrading.
This is because new Postgres versions use scram-sha-256 authentication
by default and do not support md5, as it has been deprecated.
Run the following commands after the upgrade:
{legacyAuthCustomRoles.map((role) => (
ALTER ROLE {role} WITH
PASSWORD 'newpassword';
))}
)}
{data?.target_upgrade_versions.map((version) => (
{version.postgres_version} (
{version.app_version.split('supabase-postgres-')[1]})
))}