News for hackers. Stuff that matters.
Re:OrioleDB – solving some PostgreSQL wicked problems by justinclift on Friday February 25, 2022 @06:25AM (#30466119)
Pretty much every major PG release clearly states the on-disk format isn't fixed between major versions, and is subject to change:

• https://www.postgresql.org/docs/14/upgrading.html

• https://www.postgresql.org/docs/13/upgrading.html

• https://www.postgresql.org/docs/12/upgrading.html

• https://www.postgresql.org/docs/11/upgrading.html

• https://www.postgresql.org/docs/10/upgrading.html

  For major releases of PostgreSQL, the internal data storage format is subject
  to change, thus complicating upgrades.
Re:OrioleDB – solving some PostgreSQL wicked problems by mattashii on Friday February 25, 2022 @07:13AM (#30466428)
Yes, that's more 'keeping the option open' than 'we do this regularly', and I can't seem to find any documentation that MySQL gives any better guarantee.

Note that for all of 10, 11, 12, 13 and 14 no changes have been made in the storage format of tables that made it mandatory to rewrite any user-defined schema.

I will admit that some changes have been made that make the data not forward-compatible in those versions; but MySQL seems to do that at the minor release level instead of the major release level. MySQL 8 doen't even support minor release downgrades; under PostgreSQL this works just fine.

Re:OrioleDB – solving some PostgreSQL wicked problems by hans_castorp on Friday February 25, 2022 @06:53AM (#30466298)
pg_upgrade will take care of that. And you can still run upgrade from 8.4 to 14 using the --link mode which means no data will be copied - only the system catalogs need to be re-created.