Re: How to have a smooth migration

On 5/15/25 09:29, veem v wrote: This is what Sqitch(https://sqitch.org/ ) was designed for. The biggest issue is that the data will be incrementing while you do the structural changes. How you handle that is going to depend on the question raised by

Re: How to have a smooth migration

> > > > This is what Sqitch(https://sqitch.org/) was designed for. > > The biggest issue is that the data will be incrementing while you do the > structural changes. How you handle that is going to depend on the > question raised by Peter J. Holzer: > Is this being done in place on one Postgres in

Re: How to have a smooth migration

On 5/14/25 23:09, veem v wrote: Hi, Its postgres database behind the scenes. We have a use case in which the customer is planning to migrate data from an older version (V1) to a newer version (V2). For V2, the tables will be new, but their structure will be similar to the V1 version with few

Re: How to have a smooth migration

On 5/15/25 07:09, veem v wrote: Hi, Its postgres database behind the scenes. We have a use case in which the customer is planning to migrate data from an older version (V1) to a newer version (V2). For V2, the tables will be new, but their structure will be similar to the V1 version with fe

Re: How to have a smooth migration

On 2025-05-15 11:39:39 +0530, veem v wrote: > Hi, > Its postgres database behind the scenes. > > We have a use case in which the customer is planning to migrate data from an > older version (V1) to a newer version (V2). For V2, the tables will be new, > but > their structure will be similar to th

How to have a smooth migration

Hi, Its postgres database behind the scenes. We have a use case in which the customer is planning to migrate data from an older version (V1) to a newer version (V2). For V2, the tables will be new, but their structure will be similar to the V1 version with few changes in relationship might be ther