Re: pg_upgrade from PG-14.5 to PG-15.1 failing due to non-existing function

From: Christoph Moench-Tegeder <cmt(at)burggraben(dot)net>
To: Dimos Stamatakis <dimos(dot)stamatakis(at)servicenow(dot)com>
Cc: "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: pg_upgrade from PG-14.5 to PG-15.1 failing due to non-existing function
Date: 2023-01-25 19:06:50
Message-ID: Y9F9ygEIXkCyHwsL@elch.exwg.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

## Dimos Stamatakis (dimos(dot)stamatakis(at)servicenow(dot)com):

> In our scenario we changed the permissions of this function in PG14.5
> (via an automated tool) and then pg_upgrade tries to change the
> permissions in PG15.1 as well.

Given that this function wasn't even documented and did nothing but
throw an error "function close_lb not implemented" - couldn't you
revert that permissions change for the upgrade? (if it comes to the
worst, a superuser could UPDATE pg_catalog.pg_proc and set proacl
to NULL for that function, but that's not how you manage ACLs in
production, it's for emergency fixing only).

Regards,
Christoph

--
Spare Space

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2023-01-25 19:08:04 Re: [PATCH] Make ON CONFLICT DO NOTHING and ON CONFLICT DO UPDATE consistent
Previous Message Peter Eisentraut 2023-01-25 19:06:47 Re: What object types should be in schemas?