2 個答案
- 最新
- 最多得票
- 最多評論
0
Hello,
I was able to replicate the similar behavior with the DDL statements. As a workaround for the time being you can use the below mentioned configuration.
1. create user "User_A" with password disable;
2. create table "public"."table_a" ("id" int);
3. SET enable_case_sensitive_identifier TO true;
4. alter table "public"."table_a" owner to "User_A";`
This works and can be verified from
SET enable_case_sensitive_identifier TO false;
select * from pg_tables where tableowner = 'User_A' ;
Test 2 : Username case sensitivity works with Grant statement.
create user "User_B" with password disable;
grant select on table "public"."table_a" to "User_B" ;
SET SESSION AUTHORIZATION "User_B"
select * from "public"."table_a" ;
Thank you for bringing it to our notice. We will check with our team.
0
Great, many thanks for the response and for the work-around. I was aware of the enable_case_sensitive_identifier
setting but enabling it globally will require a large refactor in our application.
Good to see that user case sensitivity works for grant statements. Perhaps this is just an isolated issue for the grant permission command. Would be great if it could be fixed. Thanks again.
已回答 8 個月前
相關內容
- 已提問 7 個月前
- AWS 官方已更新 3 年前
- AWS 官方已更新 2 年前
- AWS 官方已更新 1 年前