Page Comparison

Introduction

Prior to version 2.6.4, all our database records contained were identified by IDs which were limited to 2 billion rows.

In version 2.6.4, we have replaced, for one table, all the IDs with bigger numbers ("long" instead of "integer"). In future versions, we will replace the IDs for other tables. We take it in several steps, because we want to ensure the change of type doesn't make some data inaccessible.

Known problems

After the installation of 2.6.4, there won't be any problem anymore for the number of records, in 've performed the first step of "upgrading" those IDs to the type "long", which supports an almost-infinite number of rows, for the table AO_32F7CE_AOINTEGRATION_QUEUE (other tables will follow).

However, if you do reach the ID 2,000,000,000, the sequence that generates the ID in the database will have reached its maximum. It is not a problem anymore, since it is possible to update the sequence. However, you mst do it manually, as an administrator.

Expected error

, which contains the messages sent to Jira.

In future versions, we will change the rest of the tables.

Expected error on PostgreSQL

Only for PostgreSQL, when you reach 2 billion records in the queue, PostgreSQL will refuse to insert new messages.

Users may come to you with an error such as "The requirements couldn't be reindexed for Requirement Yogi. (...) addToQueue()":

...

Then records are not saved anymore. You must update the sequence IDs.

How to fix in Postgres

The sequence named "AO_32F7CE_AOINTEGRATION_QUEUE_ID_seq" (quotes included) must be updated to generate bigger numberstype of the column is already "big integer" and doesn't need to be changed. It's only the sequence which needs to have its max increased:

ALTER SEQUENCE "AO_32F7CE_AOINTEGRATION_QUEUE_ID_seq" AS bigint;
ALTER SEQUENCE "AO_32F7CE_AOINTEGRATION_QUEUE_ID_seq" MAXVALUE 9223372036854775807;