| Tip | title | |
|---|---|---|
| Excerpt | ||
| ||
Error PostgreSQL : This page is only necessary for customers under version 3.0.0. |
| Panel | ||
|---|---|---|
| ||
DeprecatedThis page is only necessary for customers under version 3.0.0. If you are meeting this issue, the solution is most certainly to upgade to the latest version. |
| Tip |
|---|
Nothing to do for MySQL, Microsoft SQL Server and OracleOnly PostgreSQL may require an action here, if you reach 2 billion records. Requirement Yogi 2.6.5 for Confluence and above, until 3.0. |
Introduction
Prior to version 2.6.5, all our database records were identified by IDs which were limited to 2 billion rows.
...
As a database administrator, when should I act?
At the latest, you can wait for users to raise the issue. Unfortunately, it means pages will be saved but requirements won't be updated from the moment users meet the issue.
If you want to act early, we suggest you act when the ID "2 billion" is generated in the table AO_32F7CE_AOINTEGRATION_QUEUE, since the limit is ~2.147 billion. You can check this using the tab "Usage metrics" in the Requirement Yogi administration.
It's just a sequence where you need to increase its max.
Expected error on PostgreSQL
...
Users may come to you with an error such as "The requirements couldn't be reindexed for Requirement Yogi. (...) addToQueue()":
...
Or you may see, in the logs, an error such as:
...
| Code Block |
|---|
ALTER SEQUENCE "AO_32F7CE_AOINTEGRATION_QUEUE_ID_seq" AS bigint; ALTER SEQUENCE "AO_32F7CE_AOINTEGRATION_QUEUE_ID_seq" MAXVALUE 9223372036854775807; |
| Tip |
|---|
...
That is allOnly the table AO_32F7CE_AOINTEGRATION_QUEUE has this issue, from 2.6.5 on, and for PostgreSQL only. |