Batch Postgres boundary queries to prevent excessive query size#49
Merged
Batch Postgres boundary queries to prevent excessive query size#49
Conversation
The Postgres boundary query was already operating in a transaciton, so all that was necessary was chunking the constraints to prevent the query size from growing unmangeable. In true TDD style, I added a test that failed before this fix; batching the query causes the test to pass.
lazamar
requested changes
Feb 19, 2026
lazamar
reviewed
Feb 19, 2026
- Use existing `chunksOf` - Avoid unnecessary query for last batch (with no upper bound) - Wrap batches in transaction - Does not modify/expose PostgreSQL connector internals fo rtesting
EthanRBrown
force-pushed
the
batch-boundary-queries
branch
from
f3f499b to
bbe32f1
Compare
lazamar
reviewed
Feb 20, 2026
lazamar
requested changes
Feb 21, 2026
longer pulling fully query results into memory.
Contributor
|
Approving to unblock a customer migration |
tjschutte
approved these changes
Feb 23, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
The Postgres boundary query was already operating in a transaciton, so all that was necessary was chunking the constraints to prevent the query size from growing unmangeable.
In true TDD style, I added a test that failed before this fix; batching the query causes the test to pass.