On Wed, Oct 19, 2016 at 10:03 AM, Alex Ignatov (postgrespro) <a.ignatov@xxxxxxxxxxxxxx> wrote:
Some security consideration bear in mind that DROP OWNED cant delete own
-----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@xxxxxxxxxxxxxx>
Cc: pgsql-general@xxxxxxxxxxxxxx
Subject: Re: Drop user cascade
"Alex Ignatov \(postgrespro\)" <a.ignatov@xxxxxxxxxxxxxx> 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@xxxxxxxxxxxxxx) To make
changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
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
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
>In general what stops us to do inter DBs connection like MSSQL?
It currently is not generic to PostgreSQL, but you can do that with the dblink extension/functions.
--
Melvin Davidson
I reserve the right to fantasize. Whether or not you
wish to share my fantasy is entirely up to you.![]()
I reserve the right to fantasize. Whether or not you
wish to share my fantasy is entirely up to you.
