On 2012-06-22, Виктор Егоров wrote:
> --001636eeeb987f3f6204c31480e9
> Content-Type: text/plain; charset=UTF-8
>
> Thanks, this clarifies things for me.
>
> There's DROP ROLE IF EXISTS, which I'm using.
>
that seems kind of pointless, as, if the role exists and owns anything
it's going to fail.
Thanks, this clarifies things for me.
There's DROP ROLE IF EXISTS, which I'm using.
2012/6/22 Tom Lane
>
> Roles are not considered to be part of an extension: they really can't
> be, since an extension is local to a database while a role is global to
> the whole installation. As per the docume
=?UTF-8?B?0JLQuNC60YLQvtGAINCV0LPQvtGA0L7Qsg==?= writes:
> - I've noticed, that after I DROP EXTENSION, all roles are still there in
> the database. Is this expected?
Roles are not considered to be part of an extension: they really can't
be, since an extension is local to a database while a role
Greetings.
I've developed a small extension, that is essentially a collection of
tables with a bunch of PL/pgSQL functions,
that are API for the whole thing.
Inside the extension script I am creating extra roles, and access to the
extension's functions is provided
using these extra roles.
Given e
