Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Current »

Nothing to do for MySQL, Microsoft SQL Server and Oracle

Only PostgreSQL may require an action here, if you reach 2 billion records.

Requirement Yogi 2.6.4 for Confluence and above.


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

In version 2.6.4, we'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, which contains the messages sent to Jira.

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

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

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()":

Or you may see, in the logs, an error such as:

2021-05-11 12:54:36.043 CEST [71956] ERROR:  nextval: reached maximum value of sequence "AO_32F7CE_AOINTEGRATION_QUEUE_ID_seq" (2147483647)
2021-05-11 12:54:36.043 CEST [71956] STATEMENT:  SELECT NEXTVAL('"AO_32F7CE_AOINTEGRATION_QUEUE_ID_seq"')
2021-05-11 12:54:36.044 CEST [71956] ERROR:  current transaction is aborted, commands ignored until end of transaction block
2021-05-11 12:54:36.044 CEST [71956] STATEMENT:  select 1

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

How to fix in Postgres

The type 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:


That is all

Only the table AO_32F7CE_AOINTEGRATION_QUEUE has this issue, from 2.6.4 on, and for PostgreSQL only. 

  • No labels