Skip to content

fix: forward bufsize option in export/3 recursive call#32

Merged
frerich merged 2 commits intofrerich:mainfrom
mbaertschi:fix/export-bufsize-not-forwarded-in-recursive-call
Apr 27, 2026
Merged

fix: forward bufsize option in export/3 recursive call#32
frerich merged 2 commits intofrerich:mainfrom
mbaertschi:fix/export-bufsize-not-forwarded-in-recursive-call

Conversation

@mbaertschi
Copy link
Copy Markdown
Contributor

When export/3 is called without :into, it opens a StringIO buffer and
recurses with into: set. The bufsize option was not forwarded, causing
LargeObject.open/3 to silently fall back to the 65_536 default instead
of using the configured value.

  When export/3 is called without :into, it opens a StringIO buffer and
  recurses with into: set. The bufsize option was not forwarded, causing
  LargeObject.open/3 to silently fall back to the 65_536 default instead
  of using the configured value.
@mbaertschi
Copy link
Copy Markdown
Contributor Author

@frerich could you have a look into this?

Copy link
Copy Markdown
Owner

@frerich frerich left a comment

Choose a reason for hiding this comment

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

Good catch, thanks a lot for the patch!

@frerich frerich merged commit d006c35 into frerich:main Apr 27, 2026
4 checks passed
@frerich
Copy link
Copy Markdown
Owner

frerich commented Apr 27, 2026

@mbaertschi I just released version 0.2.5 of this library, including your bugfix: https://hex.pm/packages/pg_large_objects/0.2.5

Thanks again!

@mbaertschi
Copy link
Copy Markdown
Contributor Author

Nice, thank you as well for the quick merge!

@mbaertschi mbaertschi deleted the fix/export-bufsize-not-forwarded-in-recursive-call branch April 28, 2026 06:43
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.

2 participants