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.

Sign up for GitHub

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

Jump to bottom

pgasio::recordset only supports rows of up to 4MB #3

Open
KayEss opened this issue Jun 1, 2017 · 0 comments
Open

pgasio::recordset only supports rows of up to 4MB #3

KayEss opened this issue Jun 1, 2017 · 0 comments
Labels
bug

Comments

@KayEss
Copy link
Member

KayEss commented Jun 1, 2017

Although record_block has support for setting sizes (as well as a row size hint) the recordset class doesn't make use of this. In practice this means it will fail if a single row is associated with a D message of more than 4MB in size.

The APIs around this probably also need a bit of looking at. It would be nice to be able to recycle the record_block instances as well so we don't need to allocate new ones all the time.
@KayEss KayEss added the bug label Jun 1, 2017
KayEss added a commit that referenced this issue Jun 1, 2017
@KayEss
Describe the data row size limitation.
43de661 
#3
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Milestone
No milestone
Development

No branches or pull requests
1 participant
@KayEss