Re: Drop user cascade

On Wed, Oct 19, 2016 at 10:03 AM, Alex Ignatov (postgrespro) <
a(dot)ignatov(at)postgrespro(dot)ru> wrote:

>
> -----Original Message-----
> From: pgsql-general-owner(at)postgresql(dot)org
> [mailto:pgsql-general-owner(at)postgresql(dot)org] On Behalf Of Tom Lane
> Sent: Wednesday, October 19, 2016 4:31 PM
> To: Alex Ignatov (postgrespro) <a(dot)ignatov(at)postgrespro(dot)ru>
> Cc: pgsql-general(at)postgresql(dot)org
> Subject: Re: [GENERAL] Drop user cascade
>
> "Alex Ignatov \(postgrespro\)" <a(dot)ignatov(at)postgrespro(dot)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(at)postgresql(dot)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
>
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> 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.