Re: Updating pg_attribute to change field's data type from integer to bigint on very large table

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jeff Adams <jeff(dot)adams(at)noaa(dot)gov>
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Updating pg_attribute to change field's data type from integer to bigint on very large table
Date: 2012-04-13 15:27:28
Message-ID: 24395.1334330848@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

I wrote:
> No, that is an actual on-disk change (making the field physically
> wider), so it's going to cost ya. There are some cases where the
> on-disk representation doesn't change and so a catalog update isn't
> needed, but int4->int8 isn't one of them.

Sheesh, hit send too quickly on that. Of course I meant "and so a
catalog update is all that's needed".

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Jeff Adams 2012-04-13 15:30:11 Re: Updating pg_attribute to change field's data type from integer to bigint on very large table
Previous Message Tom Lane 2012-04-13 15:03:12 Re: Updating pg_attribute to change field's data type from integer to bigint on very large table