Skip to content
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

FIX: TempEventCompare max primary key error #470

Merged
merged 1 commit into from
Dec 29, 2024
Merged

Conversation

rymarczy
Copy link
Collaborator

Staging environment is showing errors because of an sql ERROR:
nextval: reached maximum value of sequence "temp_event_compare_pk_id_seq" (2147483647)

This change restarts the identity on the TempEventCompare table to avoid a "maximum value of sequence" error.

@rymarczy rymarczy merged commit 18b1fba into main Dec 29, 2024
2 checks passed
Copy link

Coverage of commit 6e2e556

Summary coverage rate:
  lines......: 75.3% (2492 of 3309 lines)
  functions..: no data found
  branches...: no data found

Files changed coverage rate:
                                                                                     |Lines       |Functions  |Branches    
  Filename                                                                           |Rate     Num|Rate    Num|Rate     Num
  =========================================================================================================================
  src/lamp_py/performance_manager/l0_gtfs_rt_events.py                               |95.6%    135|    -     0|    -      0

Download coverage report

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant