On 7/15/21 12:46 PM, David G. Johnston wrote:
I am an application developer who operates on the principle of "change only one thing at a time".
Which pg_upgrade by definition isn't. It is bringing ALL the changes from one major version to the target version, which may be multiple at once. Including, but not limited to, catalog schema changes, SQL language changes, extension behavior changes and utility command behavior changes.
On that principle, you should advocate against using pg_upgrade in the first place.
Regards, Jan -- Jan Wieck
