| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Bharani SV-forum <esteembsv-forum(at)yahoo(dot)com> |
| Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Ver 15.X and restriction for schema=public |
| Date: | 2024-12-23 19:58:27 |
| Message-ID: | CAKFQuwbFOLniHKiv-OKCrT5yCEbSuXS-8mez2JeMzYTWsbq8sQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Monday, December 23, 2024, Bharani SV-forum <esteembsv-forum(at)yahoo(dot)com>
wrote:
>
> I am in the process of upgrading EC2-PGS ver 13.X to 15.X
> I am aware since ver 14.X, we have restriction in the usage of
> schema=public and the DBA need to grant exclusive priv for the tagged db
> user's.
>
> Any suggestions or best practise
>
The only change at that point was removing some overly permissive
defaults. You don’t need to move objects, just reinstate explicitly those
permissions that are needed that are no longer being granted by default.
You really cannot avoid the testing for a major version upgrade though.
Just expect error messages and be prepared to deal with them.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2024-12-23 20:06:37 | Re: Ver 15.X and restriction for schema=public |
| Previous Message | Bharani SV-forum | 2024-12-23 19:26:21 | Ver 15.X and restriction for schema=public |