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

Support really large objects #1875

Merged
merged 2 commits into from
Jan 15, 2024
Merged

Support really large objects #1875

merged 2 commits into from
Jan 15, 2024

Conversation

mitar
Copy link
Contributor

@mitar mitar commented Jan 14, 2024

Fixes #1865.

large_objects_test.go Outdated Show resolved Hide resolved
@jackc
Copy link
Owner

jackc commented Jan 14, 2024

The large object tests should not be parallel anymore with the changes to the global variable maxLargeObjectMessageLength. In addition, they should use a t.Cleanup() to restore the original value.

@jackc
Copy link
Owner

jackc commented Jan 14, 2024

The implementation itself is fine as far as I can tell.

@mitar
Copy link
Contributor Author

mitar commented Jan 14, 2024

The large object tests should not be parallel anymore with the changes to the global variable maxLargeObjectMessageLength. In addition, they should use a t.Cleanup() to restore the original value.

I was thinking about that, but they are all set to the same value. So does it really matter for the purpose of tests?

@mitar
Copy link
Contributor Author

mitar commented Jan 14, 2024

I updated PR and I think it is ready for review/merge.

@jackc jackc merged commit a4ca091 into jackc:master Jan 15, 2024
14 checks passed
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.

Unable to write large objects
2 participants