| From: | Mariel Cherkassky <mariel(dot)cherkassky(at)gmail(dot)com> |
|---|---|
| To: | evanbauer(at)mac(dot)com |
| Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | Re: change bigint column to int |
| Date: | 2018-11-01 12:54:07 |
| Message-ID: | CA+t6e1mBZDs34MZt7jb01S09DwW9Lwqha--+5bSQmDCss8zXbg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
I want to do it on a very big tables(100M records). Do you think that it
will be slow ? I mean if I have an AccessExclusiveLock for a lot of time I
cant just run a query and take my time until it finishes..
בתאריך יום ה׳, 1 בנוב׳ 2018 ב-13:55 מאת Evan Bauer <evanbauer(at)mac(dot)com
>:
> Mariel,
>
> Just run a query and make certain that all values currently stored in the
> column fit in 4 bytes (+/- 2,147,483,648) before doing the ALTER.
>
> Cheers,
>
> Evan
>
> Sent from my iPhone
>
> On Nov 1, 2018, at 06:20, Mariel Cherkassky <mariel(dot)cherkassky(at)gmail(dot)com>
> wrote:
>
> Hi,
>
> I want to change the column type from bigint to int to save space. By
> doing so, does it include some risks ? As I see it, I should only run
> vacuum full afterwards if I want to return space to the os right ?
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Evan Bauer | 2018-11-01 13:52:19 | Re: change bigint column to int |
| Previous Message | Evan Bauer | 2018-11-01 11:54:50 | Re: change bigint column to int |