>>>> The CREATE USER/ROLE statement got a new option: LARGEOBJECT/NOLARGEOBJECT.
>>>> It enables to controls whether the user can create a largeobject, or not.
>>> I don't think this is necessary or appropriate.
>
>> What should control privilege to create a new largeobject?
>> Or, it implicitly allows everyone to create a new one?
>
> We have not had any requests to keep people from creating LOs, so I
> think we can just implicitly allow everyone. If we were going to try
> to manage it, I don't think a role attribute is a very good solution.
> It's not grantable or inheritable, it can't be managed per-database,
> etc. So I'd leave this out until there's some popular demand.
OK, I'll keep the current behavior (it allows everyone to create it).
BTW, currently, the default ACL of largeobject allows anything for owner
and nothing for world. Do you have any comment for the default behavior?
Thanks,
--
KaiGai Kohei <kaigai@kaigai.gr.jp>
