public inbox for [email protected]
help / color / mirror / Atom feedFrom: veem v <[email protected]>
To: pgsql-general <[email protected]>
Subject: How to have a smooth migration
Date: Thu, 15 May 2025 11:39:39 +0530
Message-ID: <CAB+=1TUU2rgjNzz6T05RPwCi1xjKr=9cwhX=Jdyo4zPiakH-zQ@mail.gmail.com> (raw)
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 there. We want to have this migration approach
happen in multiple phases in which each time the delta data from version V1
will be moved to version- V2 and then final cutover will happen to V2 if
all looks good or else rollback to V1. The tables are smaller in size like
max ~100K records in tables.
My question is, is it a good idea to have an approach in which we will have
procedures created to move the delta data in every phase and schedule those
using some tasks for each table. Or any other strategy should we follow?
Also another thing to note , we have used sequences as primary keys in some
tables and they have FK relationships with other tables, so the same
sequence number in version V2 will cause issues/conflict, so how should we
handle this scenario? Should we just create new sequences with higher start
values?
Regards
Veem
view thread (5+ messages) latest in thread
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]
Subject: Re: How to have a smooth migration
In-Reply-To: <CAB+=1TUU2rgjNzz6T05RPwCi1xjKr=9cwhX=Jdyo4zPiakH-zQ@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