Re: Proposal to suppress errors thrown by to_reg*()
| От | Tatsuo Ishii |
|---|---|
| Тема | Re: Proposal to suppress errors thrown by to_reg*() |
| Дата | |
| Msg-id | 20190320.071328.485760446856666486.t-ishii@sraoss.co.jp обсуждение исходный текст |
| Ответ на | Re: Proposal to suppress errors thrown by to_reg*() (Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>) |
| Ответы |
Re: Proposal to suppress errors thrown by to_reg*()
|
| Список | pgsql-hackers |
>> I (and Hoshiai-san) concern about following case:
>>
>> # revoke usage on schema s1 from foo;
>> REVOKE
>> :
>> [connect as foo]
>> test=> select to_regclass('s1.t1')::oid;
>> ERROR: permission denied for schema s1
>
> That works in a transaction. It looks right that the actually
> revoked schema cannot be accessed.
>
> S1:foo: begin;
> S2:su : revoke usage on schema s1 from foo;
> S1:foo: select to_regclass('s1.t1')::oid;
>> to_regclass
>> -------------
>> 16418
> S2:foo: commit;
> S2:foo: select to_regclass('s1.t1')::oid;
>> ERROR: permission denied for schema s1
I'm confused. How is an explicit transaction related to the topic?
Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp
В списке pgsql-hackers по дате отправления: