Greetings,
* Dominique Devienne (ddevie...@gmail.com) wrote:
> So my goal is to delete all those "db specific" ROLEs, then the DB
> with all its schemas.
If you want to drop the database anyway.. then why not simply do that
first? Nothing can be connected to a DB that's being dropped and we
don'
On 2022-07-07 09:47:38 +0200, Dominique Devienne wrote:
> Hi. I'm struggling to delete databases because of grants to roles on
> objects of those DBs.
I don't understand this. You can drop objects (and databases containing
objects) with grants to existing roles. It would be very inconvenient if
th
On Thu, 2022-07-07 at 16:36 +0200, Dominique Devienne wrote:
> > > So my goal is to delete all those "db specific" ROLEs, then the DB
> > > with all its schemas.
> > > Which implies REVOKE'ing grants on all those "db specific" ROLEs first.
> >
> > You should not really have to revoke those manuall
On Thu, Jul 7, 2022 at 3:52 PM Tom Lane wrote:
>
> Dominique Devienne writes:
> > Hi. I'm struggling to delete databases because of grants to roles on
> > objects of those DBs.
>
> > These DBs can have a large'ish number of schemas, 100-300 is typical.
> > and define a bunch of ROLEs "specific" t
Dominique Devienne writes:
> Hi. I'm struggling to delete databases because of grants to roles on
> objects of those DBs.
> These DBs can have a large'ish number of schemas, 100-300 is typical.
> and define a bunch of ROLEs "specific" to those schemas. Normally "login user"
> ROLEs are never gran
Hi. I'm struggling to delete databases because of grants to roles on
objects of those DBs.
These DBs can have a large'ish number of schemas, 100-300 is typical.
and define a bunch of ROLEs "specific" to those schemas. Normally "login user"
ROLEs are never granted explicit access to objects, instea
