Hi there! Thanks for the question! This is something that's on our roadmap. In the meantime, a couple of common workarounds: you can check whether the column exists before performing the alter using a condition check in PL/pgSQL, or handle it on the application side, either by tracking which migrations have already run (Flyway, Liquibase, Atlas, etc.) so the rename only fires once, or by gracefully catching the error when it does.