Search Postgresql Archives

Re: Ver 15.X and restriction for schema=public

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: Ver 15.X and restriction for schema=public
From: "David G. Johnston" <david.g.johnston@xxxxxxxxx>
Date: Mon, 23 Dec 2024 12:58:27 -0700
Cc: pgsql-general <pgsql-general@xxxxxxxxxxxxxx>
In-reply-to: <1694853482.6517504.1734981981968@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> <1694853482.6517504.1734981981968@mail.yahoo.com>

On Monday, December 23, 2024, Bharani SV-forum <esteembsv-forum@xxxxxxxxx> 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.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

References:
- RE: postgresql-17.0-1 Application - silent installation Issue
  - From: JOLAPARA Urvi (SAFRAN)
- Re: Help in vetting my steps for Postgres DB upgrade from Ver 13.X to ver 15.X
  - From: Adrian Klaver
- Re: Help in vetting my steps for Postgres DB upgrade from Ver 13.X to ver 15.X
  - From: Ron Johnson
- Re: Help in vetting my steps for Postgres DB upgrade from Ver 13.X to ver 15.X
  - From: Adrian Klaver
- Re: Help in vetting my steps for Postgres DB upgrade from Ver 13.X to ver 15.X
  - From: Bharani SV-forum
- Re: Help in vetting my steps for Postgres DB upgrade from Ver 13.X to ver 15.X
  - From: Adrian Klaver
- Additional Help in vetting my steps for Postgres DB upgrade from Ver 13.X to ver 15.X
  - From: Bharani SV-forum
- Re: Additional Help in vetting my steps for Postgres DB upgrade from Ver 13.X to ver 15.X
  - From: Adrian Klaver
- Re: Additional Help in vetting my steps for Postgres DB upgrade from Ver 13.X to ver 15.X
  - From: Bharani SV-forum
- Re: Additional Help in vetting my steps for Postgres DB upgrade from Ver 13.X to ver 15.X
  - From: Adrian Klaver
- Re: Additional Help in vetting my steps for Postgres DB upgrade from Ver 13.X to ver 15.X
  - From: Bharani SV-forum
- Re: Additional Help in vetting my steps for Postgres DB upgrade from Ver 13.X to ver 15.X
  - From: Adrian Klaver
- Re: Additional Help in vetting my steps for Postgres DB upgrade from Ver 13.X to ver 15.X
  - From: Bharani SV-forum
- cannot drop a tablespace which never exists in pg_tablespace
  - From: Bharani SV-forum
- Re: cannot drop a tablespace which never exists in pg_tablespace
  - From: Adrian Klaver
- Re: cannot drop a tablespace which never exists in pg_tablespace
  - From: Bharani SV-forum
- Re: cannot drop a tablespace which never exists in pg_tablespace
  - From: Adrian Klaver
- Re: cannot drop a tablespace which never exists in pg_tablespace
  - From: Bharani SV-forum
- any tips to have restricted inbound and getting connected with postgresql dB
  - From: Y_Bharani_mbsv
- Re: any tips to have restricted inbound and getting connected with postgresql dB
  - From: Adrian Klaver
- Re: any tips to have restricted inbound and getting connected with postgresql dB
  - From: Bharani SV-forum
- Ver 15.X and restriction for schema=public
  - From: Bharani SV-forum

Prev by Date: Ver 15.X and restriction for schema=public
Next by Date: Re: Ver 15.X and restriction for schema=public
Previous by thread: Ver 15.X and restriction for schema=public
Next by thread: Re: Ver 15.X and restriction for schema=public
Index(es):
- Date
- Thread

[Index of Archives] [Postgresql Jobs] [Postgresql Admin] [Postgresql Performance] [Linux Clusters] [PHP Home] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Databases] [Postgresql & PHP] [Yosemite]