Re: Proposal to suppress errors thrown by to_reg*() - Mailing list pgsql-hackers

From Tatsuo Ishii
Subject Re: Proposal to suppress errors thrown by to_reg*()
Date
Msg-id 20190320.071328.485760446856666486.t-ishii@sraoss.co.jp
Whole thread Raw
In response to Re: Proposal to suppress errors thrown by to_reg*()  (Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>)
Responses Re: Proposal to suppress errors thrown by to_reg*()
List 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 by date:

Previous
From: Andres Freund
Date:
Subject: Re: Online verification of checksums
Next
From: Michael Paquier
Date:
Subject: Re: Offline enabling/disabling of data checksums