GitHub user MisterRaindrop edited a comment on the discussion: [Proposal] Iceberg subsystem for datalake_fdw — design proposal
That's good question. Initially, we envisioned unifying the FDW and Table AM layers. That's why we use FDW to manage catalogs and volumes. Here are potential solutions: - We could store credentials in PUBLIC and achieve isolation via GRANT USAGE ON FOREIGN SERVER / schema permissions. - Providing helper functions to expand pg_auth_members for a given role, and batch creating/syncing USER MAPPING for members of that role would also alleviate the issue. How about this? GitHub link: https://github.com/apache/cloudberry/discussions/1683#discussioncomment-16634701 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
