Add PostgreSQL Visibility index maintenance guidance#4867
Open
Krishnachaitanyakc wants to merge 1 commit into
Open
Add PostgreSQL Visibility index maintenance guidance#4867Krishnachaitanyakc wants to merge 1 commit into
Krishnachaitanyakc wants to merge 1 commit into
Conversation
Explain why the executions_visibility index footprint grows on high-volume PostgreSQL deployments (nullable b-tree Search Attribute indexes plus close-time churn) and how to manage it with REINDEX CONCURRENTLY and per-table autovacuum tuning. Adds a Maintaining Visibility index health subsection to the PostgreSQL setup guide, which previously had no maintenance guidance.
|
@Krishnachaitanyakc is attempting to deploy a commit to the Temporal Team on Vercel. A member of the Team first needs to authorize it. |
|
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documents why the
executions_visibilityindex footprint grows on high-volume PostgreSQL deployments (nullable b-tree Search Attribute indexes plus close-time churn) and how to manage it withREINDEX CONCURRENTLYand per-table autovacuum tuning. There is currently no maintenance guidance on this page.The SQL snippets were verified against the upstream v12 visibility schema on PostgreSQL 16. Motivated by temporalio/temporal#10145.
┆Attachments: EDU-6700 Add PostgreSQL Visibility index maintenance guidance