temporalio / temporalio/temporal
Postgres schema support partition table feature
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.2k
- Forks
- 1.9k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 228
Description
Is your feature request related to a problem? Please describe.
No.
Describe the solution you'd like
Most temporal sql query use shard_id as condition, for postgres database partition by hash is nice for large table.
Maybe some table partition number could be number of shards.
Describe alternatives you've considered
No.
Additional context
https://www.postgresql.org/docs/current/ddl-partitioning.html
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the PostgreSQL partitioning documentation linked in the issue and then locate Temporal's PostgreSQL schema and shard configuration entry points. No file or test is identified in the issue, so first establish where schema creation is implemented and define done as supported hash partitioning with a clear relationship between partition count and shards.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, postgresql
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100