TeamI 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
- Re: Additional Help in vetting my steps for Pos... Adrian Klaver
- Re: Additional Help in vetting my steps for Pos... Bharani SV-forum
- cannot drop a tablespace which never exists in ... Bharani SV-forum
- Re: cannot drop a tablespace which never exists... Adrian Klaver
- Re: cannot drop a tablespace which never exists... Bharani SV-forum
- Re: cannot drop a tablespace which never exists... Adrian Klaver
- Re: cannot drop a tablespace which never exists... Bharani SV-forum
- any tips to have restricted inbound and getting... Y_Bharani_mbsv
- Re: any tips to have restricted inbound and get... Adrian Klaver
- Re: any tips to have restricted inbound and get... Bharani SV-forum
- Ver 15.X and restriction for schema=public Bharani SV-forum
- Re: Ver 15.X and restriction for schema=public David G. Johnston
- Re: Ver 15.X and restriction for schema=public Adrian Klaver
- Re: Ver 15.X and restriction for schema=public Adrian Klaver
- Re: any tips to have restricted inbound and get... Ron Johnson
- Re: any tips to have restricted inbound and get... Y_Bharani_mbsv
- Re: postgresql-17.0-1 Application - silent installation ... Adrian Klaver