public inbox for [email protected]
help / color / mirror / Atom feedFrom: Adam Brusselback <[email protected]>
To: Puspendu Panda <[email protected]>
Cc: [email protected]
Subject: Re: Postgres incremental database updates thru CI/CD
Date: Thu, 20 Mar 2025 12:12:09 -0400
Message-ID: <CAMjNa7czQyZspsrNwQsapAqUUDq7=xXJyGwMhukc0XSMmsRPHA@mail.gmail.com> (raw)
In-Reply-To: <CABj6V64i-YMNRMZ2gh4U=dPrLiL4=hvUQE-0n+g1EcJP0NVROg@mail.gmail.com>
References: <CABj6V64i-YMNRMZ2gh4U=dPrLiL4=hvUQE-0n+g1EcJP0NVROg@mail.gmail.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.
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: Postgres incremental database updates thru CI/CD
In-Reply-To: <CAMjNa7czQyZspsrNwQsapAqUUDq7=xXJyGwMhukc0XSMmsRPHA@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox