| From: | Alvaro Herrera from 2ndQuadrant <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Anastasia Lubennikova <a(dot)lubennikova(at)postgrespro(dot)ru>, Stephen Frost <sfrost(at)snowman(dot)net>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pg_upgrade fails with non-standard ACL |
| Date: | 2019-09-11 21:25:38 |
| Message-ID: | 20190911212538.GA8532@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2019-Aug-21, Bruce Momjian wrote:
> > 1) How exactly should we report this incompatibility to a user?
> > I think it's fine to leave the warnings and also write some hint for the
> > user by analogy with other checks.
> > "Reset ACL on the problem functions to default in the old cluster to
> > continue"
>
> Yes, I think it is good to at least throw an error during --check so
> they don't have to find out during a live upgrade. Odds are it will
> require manual repair.
I'm not sure what you're proposing here ... are you saying that the user
would have to modify the source cluster before pg_upgrade accepts to
run? That sounds pretty catastrophic.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera from 2ndQuadrant | 2019-09-11 22:01:26 | Re: proposal - patch: psql - sort_by_size |
| Previous Message | Alvaro Herrera from 2ndQuadrant | 2019-09-11 21:23:00 | Re: pg_upgrade fails with non-standard ACL |