From: | Lok P <loknath(dot)73(at)gmail(dot)com> |
---|---|
To: | sud <suds1434(at)gmail(dot)com>, Greg Sabino Mullane <htamfids(at)gmail(dot)com> |
Cc: | pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Column type modification in big tables |
Date: | 2024-08-10 21:06:42 |
Message-ID: | CAKna9Vb0ABStAWogCsXK+jTT9ZuLESJ0_-r3Wtvd=rZpYMYwxw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Sat, Aug 10, 2024 at 5:47 PM sud <suds1434(at)gmail(dot)com> wrote:
>
>
> My 2cents.
> If you have enough time then from a simplicity point of view, your single
> line alter command may look good, but how are you going to see the amount
> of progress it has made so far and how much time it's going to take to
> finish. And you got ~6hrs of down time but if it fails at 5th hour then you
> will be in a bad position.
>
>
>
Does it mean that , if we get enough downtime then , we should rather go
with the option of recreating the table from scratch and populating the
data from the existing table and then rename it back? It does look more
complicated considering many steps like creating indexes, constraints back
and renaming it and then running vacuum and analyze etc.
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?
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2024-08-10 21:27:37 | Re: Insert works but fails for merge |
Previous Message | yudhi s | 2024-08-10 20:23:11 | Re: Insert works but fails for merge |