Re: Column type modification in big tables - Mailing list pgsql-general

From veem v
Subject Re: Column type modification in big tables
Date
Msg-id CAB+=1TV0EnXiD3FYnzbgp+zH5mC0oO2SO3sHV7aEr1-2DBXRig@mail.gmail.com
Whole thread Raw
In response to Re: Column type modification in big tables  (Greg Sabino Mullane <htamfids@gmail.com>)
List pgsql-general

On Tue, 13 Aug 2024 at 19:39, Greg Sabino Mullane <htamfids@gmail.com> wrote:
On Sat, Aug 10, 2024 at 5:06 PM Lok P <loknath.73@gmail.com> wrote:
 
Can someone through some light , in case we get 5-6hrs downtime for this change , then what method should we choose for this Alter operation?

We can't really answer that. Only you know what resources you have, what risk/reward you are willing to handle, and how long things may take. For that latter item, your best bet is to try this out on the same/similar hardware and see how long it takes. Do a smaller table and extrapolate if you need to. Or promote one of your replicas offline and modify that. I've given you a low-risk / medium-reward option with check constraints, but for the ALTER TABLE options you really need to try it and see (on non-prod).


What about if the OP opt a strategy something as below,
1) Detaching the partitions 2)Altering individual partitions with required column type and length 3)Altering the table 4)Attaching the partitions back to the main table

This should be faster and also a controlled fashion for each partition individually. 

pgsql-general by date:

Previous
From: Lok P
Date:
Subject: Re: Column type modification in big tables
Next
From: "Peter J. Holzer"
Date:
Subject: Re: Column type modification in big tables