Message-ID: <5a747f00-02dc-3922-6506-fef8ccd701bf@gmail.com>
Date: Thu, 28 Jul 2022 12:41:41 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
 Thunderbird/91.9.1
Subject: Re: What to watch out for when ALTERing NUMERIC(38,0) to BIGINT?
Content-Language: en-US
To: pgsql-admin <pgsql-admin@lists.postgresql.org>
References: <a4465ae0-574a-1727-fcdd-1dac49b874c0@gmail.com>
 <CAKFQuwZ8su=VAeyNZ6Wj5cU1OoZLQB+B3iPWh49k2yjk4o4ujQ@mail.gmail.com>
 <3421791.1659021999@sss.pgh.pa.us>
From: Ron <ronljohnsonjr@gmail.com>
In-Reply-To: <3421791.1659021999@sss.pgh.pa.us>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: 
 <https://www.postgresql.org/message-id/5a747f00-02dc-3922-6506-fef8ccd701bf%40gmail.com>
Precedence: bulk

On 7/28/22 10:26, Tom Lane wrote:
> "David G. Johnston" <david.g.johnston@gmail.com> writes:
>> On Thu, Jul 28, 2022 at 8:13 AM Ron <ronljohnsonjr@gmail.com> wrote:
>>> Besides what's mentioned in
>>> https://www.postgresql.org/docs/12/ddl-alter.html#id-1.5.4.8.10, what
>>> happens *internally* when I run:
>>> ALTER TABLE foo ALTER COLUMN bar TYPE BIGINT;
>> IIUC, that would be the silver lining in all of this - the rewritten table
>> would have zero fragmentation and bloat.
> Yeah.  What happens internally is a table rewrite: the entire content
> of the table (and its indexes) is written into a new set of files.
> At commit, the old files are deleted.  The main gotchas, for a large
> table, are the transient disk space consumption and the fact that the
> table stays exclusively locked the whole time.

Rewriting a 3TB table doesn't seem appetizing.  Fortunately, there's only 
one table like that...

-- 
Angular momentum makes the world go 'round.