Ver 15.X and restriction for schema=public
| От | Bharani SV-forum |
|---|---|
| Тема | Ver 15.X and restriction for schema=public |
| Дата | |
| Msg-id | 1694853482.6517504.1734981981968@mail.yahoo.com обсуждение исходный текст |
| Ответ на | Re: any tips to have restricted inbound and getting connected with postgresql dB (Bharani SV-forum <esteembsv-forum@yahoo.com>) |
| Ответы |
Re: Ver 15.X and restriction for schema=public
Re: Ver 15.X and restriction for schema=public |
| Список | pgsql-general |
Team
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.
Assume i want to enforce it,
Can i retag all the object tables/indexex/packages/procedures/functions etc tagged under schema =public to a newly created schema e.g = schemaname = allowallusr and grant respective priv's.
Whether it will resolve the issue, as application time need time to validated all the use case for testing the objects which is present under schema=public and ported to new schema= allowallusr .
Any suggestions or best practise
В списке pgsql-general по дате отправления: