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

crash on linux when selecting columns after inserting large blobs #570

Open
PThorpe92 opened this issue Dec 28, 2024 · 0 comments
Open

crash on linux when selecting columns after inserting large blobs #570

PThorpe92 opened this issue Dec 28, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@PThorpe92
Copy link
Contributor

PThorpe92 commented Dec 28, 2024

In the process of running some tests for batch processing of writes in #557, I did something like:

INSERT INTO t (t1, t2) VALUES (zeroblob(4096*4096), zeroblob(4096*1024));

As usual, I would open the .db file in sqlite3, and make sure I could run .schema, and a select * from t;, to ensure it did not corrupt the db file with partial writes. While sqlite3 had no issue with this, limbo crashed on select * from t and I was worried at first it was an issue with the changes I had made to the linux IO module.

I re-built limbo from main and attempted again and this problem persists. I created a new .db file with sqlite3 with similar blob inserts, again on the main branch with the same outcome.

image

I'll be working on this, as it's adjacent to the other io issue.

EDIT: *confirmed this isn't a problem with in-memory IO. I'll see if I can get someone to try on a mac. confirmed not a problem on mac as well.

@penberg penberg added the bug Something isn't working label Dec 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants