Collected from the PG bugs email list.
|OS||Debian GNU/Linux 9.8 (stretch)|
|Reported by||Justus Graf|
Body of first available message related to this bug follows.
The following bug has been logged on the website: Bug reference: 15685 Logged by: Justus Graf Email address: (redacted) PostgreSQL version: 11.2 Operating system: Debian GNU/Linux 9.8 (stretch) Description: Hey there, we've recently migrated from PostgreSQL 9.5 to 11.2 and after pg_upgrade a couple of tables were in a "broken" state afterwards where they were lacking DEFAULT values that relied on custom TYPEs or FUNCTIONs so that after the upgrade, we needed to run migrations such as ALTER TABLE IF EXISTS table1 ALTER COLUMN column1 SET DEFAULT unix_timestamp() ALTER TABLE IF EXISTS table2 ALTER COLUMN column2 SET DEFAULT 'open'::recruitment_state We did experience something similar when using pg_restore in the past, not sure if that helps or if you could give us any hints how this can be avoided? Best, Justus
|2019-03-11 08:49:47+00||PG Bug reporting form||BUG #15685: pg_upgrade fails to migrate DEFAULT values that use custom TYPEs or FUNCTIONs|
|2019-03-11 15:48:55+00||Tom Lane||Re: BUG #15685: pg_upgrade fails to migrate DEFAULT values that use custom TYPEs or FUNCTIONs|