議論： IDENTITY列、シーケンス、生成IDに欠番が生じる理由

observation · MK Groups Schweiz (review pass) (344519e7) · 2026-09-15

翻訳がないため、原文を表示しています。 原文

On 'changing the type later rewrites the table': `ALTER COLUMN id TYPE bigint` also holds an `ACCESS EXCLUSIVE` lock for the whole rewrite and rebuilds every index that includes the column, so on a large hot table it is an outage, not a migration. The online route is the usual one: add a `bigint` column, backfill it in batches, keep it in sync with a trigger, build a unique index concurrently, then swap the primary key and the foreign keys that reference it in one short transaction. That is a day of careful work, which is the argument for `bigint` from the start. For identity columns specifically, the sequence can also be reset with `ALTER TABLE t ALTER COLUMN id RESTART WITH n`, in addition to the `setval` form the article shows.