public inbox for [email protected]
help / color / mirror / Atom feedFrom: veem v <[email protected]>
To: Adrian Klaver <[email protected]>
To: Peter J. Holzer <[email protected]>
Cc: pgsql-general <[email protected]>
Subject: Re: How to have a smooth migration
Date: Thu, 15 May 2025 21:59:26 +0530
Message-ID: <CAB+=1TV7J-ORtH8EtbuqbheLdSRsw4YBh+Cw38X5cfRbQsTUnQ@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <CAB+=1TUU2rgjNzz6T05RPwCi1xjKr=9cwhX=Jdyo4zPiakH-zQ@mail.gmail.com>
<[email protected]>
>
>
>
> 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 instance or between
> separate Postgres instances?
>
>
>
Thank you. Yes, these tables are going to be part of the same database.
Never use sqitch though , but was wondering if we can do it with the stored
simple proc as the number of table is very small <20 and also the max size
of table in <50MB. Also , missed to add , this is a cloud RDS database and
so not sure we can have this tool there.
To answer the questions specifically raised by Peter J. Holzer .
*Are V1 and V2 different databases or do plan to do this in-place?*Answer:-
Yes both the versions of the table are in the same database.
*What is the purpose of doing it in multiple phases? Do you have lengthy
acceptance tests during which new data will accumulate?*
Answer:-
Yes. Actually there will be a test kind of thing happen with the new code
pointing to version V2 tables and to get comfortable. But teh delta data
will be very small.
*By "rollback" do mean a transaction rollback or some other means of
restoring the previous state?*Answer:-
"rollbak" means pointing the old code back to the version V1 tables.
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], [email protected], [email protected]
Subject: Re: How to have a smooth migration
In-Reply-To: <CAB+=1TV7J-ORtH8EtbuqbheLdSRsw4YBh+Cw38X5cfRbQsTUnQ@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