Date: Mon, 23 Dec 2024 19:26:21 +0000 (UTC)
From: Bharani SV-forum <esteembsv-forum@yahoo.com>
To: pgsql-general <pgsql-general@postgresql.org>
Message-ID: <1694853482.6517504.1734981981968@mail.yahoo.com>
In-Reply-To: <2036867199.5856152.1734735063013@mail.yahoo.com>
References: <0558ddd4d71641bdb41fa49b2425f73c@safrangroup.com> <273a88dc-4134-47d5-bc19-30ff5f97926c@aklaver.com> <CANzqJaC1Uk4H=55vV_jbFYMuD1f9Bb_4Y9WKvkZA3bt92bEUnw@mail.gmail.com> <498dfb34-4dd7-4f48-8188-355e1488d7e6@aklaver.com> <1061066336.5835157.1733316137292@mail.yahoo.com> <a779ef21-f04d-4a51-83d3-51632b0fb3fa@aklaver.com> <1918413683.2239751.1733944364448@mail.yahoo.com> <037a8338-3434-47d4-aaad-ef186d4d3250@aklaver.com> <101139100.4053671.1734383960480@mail.yahoo.com> <dece41b2-44bd-4b0c-9b3e-57b0adfaf1bb@aklaver.com> <1875422740.4095620.1734388259706@mail.yahoo.com> <aa16f097-fadd-439c-a58e-e2229d92bc5b@aklaver.com> <1528119631.4096246.1734390318281@mail.yahoo.com> <2033286177.1733661.1734651404850@mail.yahoo.com> <8833d8c7-3713-4d6f-9eab-35270e769564@aklaver.com> <1392047062.5689697.1734710997053@mail.yahoo.com> <adc3d09b-440c-48c7-9d72-0f247f27feff@aklaver.com> <783439164.5695290.1734713539262@mail.yahoo.com> <928427177.4710979.1734722745840@mail.yahoo.com> <f37731a5-80bf-45d8-b699-587652f34b00@aklaver.com> <2036867199.5856152.1734735063013@mail.yahoo.com>
Subject: Ver 15.X and restriction for schema=public
MIME-Version: 1.0
Content-Type: multipart/alternative; 
	boundary="----=_Part_6517503_178521388.1734981981967"
Content-Length: 2360
Archived-At: <https://www.postgresql.org/message-id/1694853482.6517504.1734981981968%40mail.yahoo.com>
Precedence: bulk

------=_Part_6517503_178521388.1734981981967
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

 TeamI am in the process of upgrading EC2-PGS ver 13.X to 15.X=C2=A0I am aw=
are=C2=A0 since ver 14.X, we have restriction in the usage of schema=3Dpubl=
ic 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/packa=
ges/procedures/functions etc tagged under schema =3Dpublic to a newly creat=
ed schema e.g =3D schemaname =3D allowallusr and grant respective priv's.
Whether it will resolve the issue, as application time need time to validat=
ed all the use case for testing the objects which is present under schema=
=3Dpublic and ported to new schema=3D allowallusr .
Any suggestions or best practise
------=_Part_6517503_178521388.1734981981967
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<html><head></head><body><div class=3D"ydp916420yahoo-style-wrap" style=3D"=
font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;"><=
div></div>
        <div dir=3D"ltr" data-setdir=3D"false">Team</div><div dir=3D"ltr" d=
ata-setdir=3D"false">I am in the process of upgrading EC2-PGS ver 13.X to 1=
5.X&nbsp;</div><div dir=3D"ltr" data-setdir=3D"false">I am aware&nbsp; sinc=
e ver 14.X, we have restriction in the usage of schema=3Dpublic and the DBA=
 need to grant exclusive priv for the tagged db user's.</div><div dir=3D"lt=
r" data-setdir=3D"false"><br></div><div dir=3D"ltr" data-setdir=3D"false">A=
ssume i want to enforce it,</div><div dir=3D"ltr" data-setdir=3D"false">Can=
 i retag all the object tables/indexex/packages/procedures/functions etc ta=
gged under schema =3Dpublic to a newly created schema e.g =3D <b>schemaname=
 =3D allowallusr </b>and grant respective priv's.</div><div dir=3D"ltr" dat=
a-setdir=3D"false"><br></div><div dir=3D"ltr" data-setdir=3D"false">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=3Dpublic=
 and ported to new schema=3D allowallusr .</div><div dir=3D"ltr" data-setdi=
r=3D"false"><br></div><div dir=3D"ltr" data-setdir=3D"false">Any suggestion=
s or best practise</div></div></body></html>
------=_Part_6517503_178521388.1734981981967--