Bigint Migration for 'events' Table (Step 3) #4406
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
philippthun
force-pushed
the
bigint-migration-events-step3
branch
2 times, most recently
from
6aaf1df to
29d1456
Compare
philippthun
force-pushed
the
bigint-migration-events-step3
branch
from
29d1456 to
5ef5cc8
Compare
philippthun
force-pushed
the
bigint-migration-events-step3
branch
2 times, most recently
from
e8e1df1 to
4c39d2d
Compare
philippthun
force-pushed
the
bigint-migration-events-step3
branch
2 times, most recently
from
1ff66d5 to
fa979b0
Compare
- implementation of steps 3a and 3b for the events table - step 3a: add check constraint (NOT VALID) / run VALIDATE CONSTRAINT separately with longer timeout and less restrictive locks - step 3b: drop check constraint and trigger function / drop old id column / switch id_bigint -> id (index added concurrently) - down migration fully implemented for testing purposes - added comments to step 1 and step 3b down migrations - they should not be used in a production system
philippthun
force-pushed
the
bigint-migration-events-step3
branch
from
fa979b0 to
18b25b9
Compare
johha
approved these changes
Jul 23, 2025
ari-wg-gitbot
added a commit
to cloudfoundry/capi-release
that referenced
this pull request
Jul 23, 2025
Changes in cloud_controller_ng:
- Bigint Migration for 'events' Table (Step 3)
PR: cloudfoundry/cloud_controller_ng#4406
Author: Philipp Thun <philipp.thun@sap.com>
jochenehret
added a commit
that referenced
this pull request
Oct 2, 2025
* step 3a and b for remaining tables: jobs, delayed_jobs, app_usage_events, service_usage_events * see also #4406
5 tasks
jochenehret
added a commit
that referenced
this pull request
Oct 2, 2025
* step 3a and b for remaining tables: jobs, delayed_jobs, app_usage_events, service_usage_events * see also #4406
jochenehret
added a commit
that referenced
this pull request
Oct 2, 2025
* step 3a and b for remaining tables: jobs, delayed_jobs, app_usage_events, service_usage_events * see also #4406
jochenehret
added a commit
that referenced
this pull request
Oct 2, 2025
* step 3a and b for remaining tables: jobs, delayed_jobs, app_usage_events, service_usage_events * see also #4406
jochenehret
added a commit
that referenced
this pull request
Oct 2, 2025
* step 3a and b for remaining tables: jobs, delayed_jobs, app_usage_events, service_usage_events * see also #4406
jochenehret
added a commit
that referenced
this pull request
Oct 13, 2025
* step 3a and b for remaining tables: jobs, delayed_jobs, app_usage_events, service_usage_events * see also #4406
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
NOT VALID) / runVALIDATE CONSTRAINTseparately with longer timeout and less restrictive locksidcolumn / switchid_bigint->id(index added concurrently)I have reviewed the contributing guide
I have viewed, signed, and submitted the Contributor License Agreement
I have made this pull request to the
mainbranchI have run all the unit tests using
bundle exec rakeI have run CF Acceptance Tests