Re: Drop user cascade - Mailing list pgsql-general

From Alex Ignatov \(postgrespro\)
Subject Re: Drop user cascade
Date
Msg-id 035801d22a11$8c6f9820$a54ec860$@postgrespro.ru
Whole thread Raw
In response to Re: Drop user cascade  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Drop user cascade
List pgsql-general
-----Original Message-----
From: pgsql-general-owner@postgresql.org
[mailto:pgsql-general-owner@postgresql.org] On Behalf Of Tom Lane
Sent: Wednesday, October 19, 2016 4:31 PM
To: Alex Ignatov (postgrespro) <a.ignatov@postgrespro.ru>
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Drop user cascade

"Alex Ignatov \(postgrespro\)" <a.ignatov@postgrespro.ru> writes:
> Why do Postgres have no such functionality as DROP USER CASCADE? Is
> there any reasons in that absence?

The short answer is that DROP USER couldn't reach across databases to get
rid of owned objects in other databases.  See

https://www.postgresql.org/docs/9.6/static/role-removal.html

            regards, tom lane


--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make
changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general


Some security consideration bear in mind that DROP OWNED cant delete  own
objects in other DBs? In general what stops  us  to do inter DBs connection
like MSSQL?

--
Alex Ignatov
Postgres Professional: http://www.postgrespro.com The Russian Postgres
Company



pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Drop user cascade
Next
From: Merlin Moncure
Date:
Subject: Re: json rendering without pretty option (compact)