Skip to content

fix: set postgres queue offset as a bigint #10344

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

Skraye
Copy link
Member

@Skraye Skraye commented Jul 25, 2025

No description provided.

@github-project-automation github-project-automation bot moved this to To review in Pull Requests Jul 25, 2025
@Skraye Skraye requested review from loicmathieu and Copilot and removed request for Copilot July 25, 2025 07:19
Copy link

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR fixes a data type issue by changing the PostgreSQL queue offset from a standard integer to a bigint to handle larger offset values.

Key Changes

  • Updates the database sequence to use BIGINT data type
  • Sets the maximum value for the sequence to the BIGINT limit
  • Alters the table column to use BIGINT type

@Skraye Skraye force-pushed the fix/postgres-offset-bigint branch from 6bde4f0 to 2b153d4 Compare July 25, 2025 07:28
Copy link
Member

@loicmathieu loicmathieu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, should be backported at least to 0.23 and 0.22

@Skraye Skraye force-pushed the fix/postgres-offset-bigint branch from 2b153d4 to 5f8017d Compare July 25, 2025 09:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: To review
Development

Successfully merging this pull request may close these issues.

2 participants