Re: Gradual migration from integer to bigint? - Mailing list pgsql-general

From Ireneusz Pluta
Subject Re: Gradual migration from integer to bigint?
Date
Msg-id 624e0261-2c7b-01cf-ec30-3c1e04af2b89@wp.pl
Whole thread Raw
In response to Gradual migration from integer to bigint?  (James Healy <james@yob.id.au>)
Responses Re: Gradual migration from integer to bigint?  (Ron <ronljohnsonjr@gmail.com>)
List 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.



pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: cache lookup failed for function 0
Next
From: Ron
Date:
Subject: Re: Gradual migration from integer to bigint?