Dear PostgreSQL Community Team,
I am working on a project that uses libpq along with C language to interact with PostgreSQL, and we face challenges with managing schema changes dynamically in production while avoiding downtime. Specifically, we need guidance on handling table structure changes/additions without tightly coupling these changes to application updates.
Current Approach:
Schema changes are deployed first, followed by application updates to align with the new structure.
Challenges:
Ensuring application stability during the transitional phase when the schema and code are not fully in sync.
Handling table structure changes (e.g., adding new columns) dynamically without requiring immediate code changes.
Questions:
Are there recommended best practices for managing such schema changes with libpq?
How can we efficiently handle table additions/updates while keeping the application and database in sync dynamically?
I would appreciate any guidance, patterns, or examples that can help us implement a robust solution.
Thank you for your time and support!
Regards,
Sasmit Utkarsh
+91-7674022625
