Re: Gradual migration from integer to bigint?

From: Ireneusz Pluta <ipluta(at)wp(dot)pl>
To: James Healy <james(at)yob(dot)id(dot)au>, pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Gradual migration from integer to bigint?
Date: 2023-10-01 17:04:42
Message-ID: 624e0261-2c7b-01cf-ec30-3c1e04af2b89@wp.pl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

W dniu 30.09.2023 o 07:55, James Healy pisze:
> ...
> We shouldn't have let them get so big, but that's a conversation
> for another day.
>
> Some are approaching overflow and we're slowly doing the work to
> migrate to bigint. Mostly via the well understood "add a new id_bigint
> column, populate on new tuples, backfill the old, switch the PK"
> method. The backfill is slow on these large tables, but it works and
> there's plenty of blog posts and documentation to follow.
wouldn't wrapping to negative numbers like: https://www.youtube.com/watch?v=XYRgTazYuZ4&t=1338s be a
solution for you? At least for buying more time for the slow migration process. Or even as a
definite solution if you now take care and not let the keys grow too quickly.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Ron 2023-10-01 22:47:54 Re: Gradual migration from integer to bigint?
Previous Message Tom Lane 2023-10-01 14:32:33 Re: cache lookup failed for function 0