perf(tapd): optimize migration script 20230411 for PostgreSQL (22s → 4s)#8677
Merged
perf(tapd): optimize migration script 20230411 for PostgreSQL (22s → 4s)#8677
Conversation
…data Reduce PostgreSQL migration time from 22s to 4s by: 1. Cache column metadata per table instead of querying information_schema for each column check (270 queries → 3 queries) 2. Batch PostgreSQL cache clearing (135 SELECTs → 3 SELECTs) 3. Handle PostgreSQL and MySQL syntax differences appropriately The key optimization is fetching all column names once via GetColumns() and using a map for O(1) lookups instead of calling HasColumn() twice per column rename operation. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
d4x1
approved these changes
Jan 8, 2026
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.
Problem
#8676
Root cause:
Solution
Optimized the migration by:
- PostgreSQL: Execute separate ALTER TABLE ... RENAME COLUMN statements (required by syntax)
- MySQL: Use single ALTER TABLE with multiple CHANGE COLUMN clauses
Performance Impact
Testing
Performance comparison
Schema validation
mysql
Postgres