Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
Description
According to current implementation user who uses HCatalog integration feature should have SELECT privileges for pg_authid, pg_user_mapping tables.
It's fine for superusers but we shouldn't expose them to non-superusers because they store hashed user passwords.
Basically, the problem is how to determine max oid among all oid-having tables.
Possible solutions:
- Creating view returning max oid and grant select privilege to public.
- Cons:
- Requires catalog upgrade;
- Cons:
- Reading current oid from shared memory.
- Pros:
- No catalog upgrade needed.
- Cons:
- Additional exclusive locks needed.
- Pros:
Attachments
Issue Links
- links to