| From: | Moreno Andreo <moreno(dot)andreo(at)evolu-s(dot)it> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PostgreSQL mailing lists <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: REVOKE to an user that doesn't exist |
| Date: | 2018-12-17 15:02:24 |
| Message-ID: | 2f1b90d6-9868-96fa-ab2e-1bb8713b52f2@evolu-s.it |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Il 12/12/2018 16:01, Tom Lane ha scritto:
>
> The safest way to clean it up manually would be to set the pg_proc.proacl
> field for that function to NULL. If there are other grants about the
> function, you could try removing the bad entry, but it would likely be
> safer to just re-grant after the upgrade.
>
Setting the column (and several others from other tables such as
pg_class) to null made me possible to upgrade the cluster. After the
upgrade, I issued the necessary GRANTs and everything is up & running on
Postgres 10 now!
Thanks again
Moreno.-
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Verite | 2018-12-17 15:35:41 | Re: Creating 2D arrays for pg_copy_from, reading tab-delimted text file that contains comma and double quotes |
| Previous Message | Jerry Sievers | 2018-12-17 15:01:10 | Re: conditionally terminate psql script |