Thread: Postgres incremental database updates thru CI/CD
Hi ,
As my organization started working on postgres database,We are facing some difficulties in creating CI/CD pipeline for deployment updated script(the updated changes after base line database) .Earlier we used sql server database and in sqlserver we have one option called DACPAC(Data-tier Application Package) thru which we can able to generate update script and thru CI/cd pipeline we automate deployment process in destination database (customer).
But in Postgres I didn't find any such tool like DACPAC .
As we need this process to incrementally update the customer database can you help us in this regard .
Thanks & Regards,
Puspendu
On 3/19/25 11:07, Puspendu Panda wrote: > Hi , > As my organization started working on postgres database,We are facing > some difficulties in creating CI/CD pipeline for deployment updated > script(the updated changes after base line database) .Earlier we used > sql server database and in sqlserver we have one option called > DACPAC(Data-tier Application Package) thru which we can able to generate > update script and thru CI/cd pipeline we automate deployment process in > destination database (customer). > But in Postgres I didn't find any such tool like DACPAC . https://sqitch.org/ > As we need this process to incrementally update the customer database > can you help us in this regard . > Thanks & Regards, > Puspendu -- Adrian Klaver adrian.klaver@aklaver.com
There are no built in tools for this in Postgres.
There are other tools like the one mentioned that you can use instead. I've used Liquibase for migrations for multiple companies now and it works well enough.If you have to support rollbacks for your deployments, that is a pretty manual process for any serious migration (especially migrations requiring data movement) in my experience. Also set up something that requires all PRs to be able to apply update, rollback, and apply update again and still be in the same state as if you only applied the update once.
For my current project, I have my liquibase integrated with my Spring Boot backend, and CI/CD just deploys that artifact and on startup of the backend the migrations are run. At my last company the liquibase portion was standalone because we had a single database that had multiple products interacting with it and we needed to be able to handle migrations separately than any one specific app, so that was deployed directly through CI/CD.