Re: Gradual migration from integer to bigint?
От | Ireneusz Pluta |
---|---|
Тема | Re: Gradual migration from integer to bigint? |
Дата | |
Msg-id | 624e0261-2c7b-01cf-ec30-3c1e04af2b89@wp.pl обсуждение исходный текст |
Ответ на | Gradual migration from integer to bigint? (James Healy <james@yob.id.au>) |
Ответы |
Re: Gradual migration from integer to bigint?
|
Список | 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 по дате отправления: