From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Pavel Golub <pavel(at)gf(dot)microolap(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: proposal: regrole type? |
Date: | 2012-12-26 07:30:12 |
Message-ID: | CAFj8pRCGr4rWKPuD-vgeyRCzvrqopz_5kK_C1gcvX9d382CTig@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2012/12/25 Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>:
> Hello
>
> 2012/12/25 Pavel Golub <pavel(at)microolap(dot)com>:
>> Hello, Pavel.
>>
>> You wrote:
>>
>> PS> Hello
>>
>> PS> Can we implement REGROLE type, that simplify role name <-> oid transformations?
>>
>> +1 from me. My old wish.
>
> I started implementation. I found a two points, that should be solved before.
>
> we operate over roles with (without) fictive role "public". So we need
> two datatypes :( I have no idea about second name :( - there should be
> difference if type enables or disallow "public".
>
> second issue is value of ACL_ID_PUBLIC, that is zero - and there is
> not difference from InvalidOid - what should be acceptable via "-"
> symbol.
>
> Any ideas?
one idea
regrole - defined only for "real" roles - support InvalidOid - doesn't
support "public"
regaclrole - defined for any roles, that can be used for ACL (with
"public"), doesn't support InvalidOid
Regards
Pavel
>
> Regards
>
> Pavel
>
>>
>> PS> Regards
>>
>> PS> Pavel
>>
>>
>>
>>
>>
>> --
>> With best wishes,
>> Pavel mailto:pavel(at)gf(dot)microolap(dot)com
>>
From | Date | Subject | |
---|---|---|---|
Next Message | Jeevan Chalke | 2012-12-26 14:54:57 | Re: too much pgbench init output |
Previous Message | Pavel Stehule | 2012-12-26 07:25:05 | Re: proposal: regrole type? |