Preserve long PostgreSQL index expressions - #37
Draft
Josh-McFarlin wants to merge 1 commit into
Draft
Josh-McFarlin wants to merge 1 commit into
Josh-McFarlin wants to merge 1 commit into
Conversation
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
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.
Summary
Preserves PostgreSQL index expressions longer than the 63-byte identifier limit during introspection.
What changed
pg_attribute.attnametotextbefore coalescing it withpg_get_indexdef.Validation
Stack
This PR targets the existing
0.32.4release head so the release version remains the stack parent.Rollout and rollback
This PR does not publish a package or update a consumer. Reverting it restores the prior introspection query.
~ written by Replit Agent