dosubot[bot] commented on issue #30678: URL: https://github.com/apache/superset/issues/30678#issuecomment-2430389450
<!-- Answer --> If the "pgsql" schema is set up the same way as other schemas but is not appearing in the permissions list, consider the following possibilities: 1. **Permission Synchronization**: Ensure that the permissions for the "pgsql" schema are synchronized with Superset. Sometimes, changes in the database might not immediately reflect in Superset. You can try refreshing the metadata or restarting the Superset server to see if this resolves the issue. 2. **Schema Naming or Pattern**: Check if there is any specific logic in Superset that handles schema visibility differently for certain schema names or patterns. Although I couldn't find specific logic for schema name patterns, it's worth reviewing any custom configurations or scripts that might affect schema visibility. 3. **Database Connection and Catalog**: Verify that the database connection and catalog settings are correctly configured. If the "pgsql" schema is associated with a non-default catalog, it might be excluded from the permissions list due to the logic in the `downgrade_schema_perms` function, which deletes permissions for non-default catalogs <sup>[[1]](https://github.com/apache/superset/blob/master/superset/migrations/shared/catalogs.py)</sup>. 4. **Superset Logs**: Check the Superset logs for any errors or warnings related to schema permissions. This might provide insights into why the "pgsql" schema is not appearing. If none of these steps resolve the issue, consider reviewing the Superset codebase or configurations for any custom logic that might affect schema visibility. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
