You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should roll this back so that it is more compatible with other pg variants.
However, we need to be careful here as we ran into issues where READ access was not always sufficient to see the metadata from those tables. I think we also need USAGE on the table/schema to see more informationa bout it.
The permissions modal should maybe still use the pg_catalog queries.
We just need to be explicit about logging what permissions we need the users to have so that we can see everything we need to see.
We should roll this back so that it is more compatible with other pg variants.
However, we need to be careful here as we ran into issues where READ access was not always sufficient to see the metadata from those tables. I think we also need USAGE on the table/schema to see more informationa bout it.
The permissions modal should maybe still use the pg_catalog queries.
We just need to be explicit about logging what permissions we need the users to have so that we can see everything we need to see.
We have this page that details permissions for a role: https://docs.neosync.dev/connections/postgres#source-connections
We should make sure these continue to work well when migrating back to the information_schema queries
From SyncLinear.com | NEOS-1134
The text was updated successfully, but these errors were encountered: