Closed demanuel closed 2 years ago
Can you provide a CREATE TABLE statement and INSERT with a value that causes the error?
There is at least some support for bytea data.
test.txt File attached (it's a sql file but github didn't allowed me to upload it with the sql extension).
The first 15 to 20 inserts are different and then i just copy pasted. The interesting thing is that the problem occurs only if i have a certain amount of records in the DB. If i have less than X records i have no problem.
I don't have time now, but later if required i will provide the threshold number X.
Ah, fun.
I'm able to reproduce on moar-2022.03 but moar-2021.12 works as expected (fails with a different error at 1.9 million entries).
I'll try to narrow it down further.
So, the value doesn't matter. A completely empty value works too.
my @rows = $dbh.execute(q{select ''::bytea from (SELECT * from generate_series(1, 5000)) as series(c)}).allrows;
Also, the exact number of entries required to cause the fault varies a bit, anywhere between 280 to 512 but ~340 is most common.
I believe this is a NativeCall dispatch error that shows itself when JIT kicks in but have no idea how to debug/fix such a thing.
I've forwarded what I could:
THanks for the help and the amazing debugging skills. :-)
Confirmed to be a bug in upstream code, so I'm closing this ticket.
Hi!
I first detected this on https://github.com/CurtTilmes/raku-dbpg/issues/17 so i decided to migrate to DBIish, but it looks like it suffers of the same.
Sorry if i shouldn't report it here as well....
Issue:
DBIish dies while executing a select on a table with column type bytea:
No issues if in the select there's no "bytea" type field.
Regards, David Santiago