Hi Team,
I’ve been setting up Temporal with PostgreSQL and noticed that the database names temporal and temporal_visibility are hardcoded in the codebase. It seems there is no support for using a single database with multiple schemas instead.
- temporal/schema/postgresql/v12/temporal/database.sql at main · temporalio/temporal · GitHub
- temporal/schema/postgresql/v12/visibility/database.sql at main · temporalio/temporal · GitHub
This limitation makes it challenging to manage Temporal in environments where database consolidation is preferred, such as cloud-managed database services that impose limits on the number of databases.
I’d like to understand:
- Is there any plan to introduce schema-level abstraction so that both Temporal and Visibility data can exist within different schemas in a single database?
- What are the technical challenges in supporting this approach?
- Would the community be open to a contribution that enables schema-level configuration for Temporal databases?
Looking forward to your insights!