From: | Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp> |
---|---|
To: | horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp |
Cc: | ishii(at)sraoss(dot)co(dot)jp, hoshiai(at)sraoss(dot)co(dot)jp, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Proposal to suppress errors thrown by to_reg*() |
Date: | 2019-03-19 22:13:28 |
Message-ID: | 20190320.071328.485760446856666486.t-ishii@sraoss.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2019-03-19 23:09:07 | Re: Offline enabling/disabling of data checksums |
Previous Message | Andres Freund | 2019-03-19 21:44:52 | Re: Online verification of checksums |