So, how exactly it works for other people ? Shouldnt everyone who use this extension should have suffered from this bug ? And why for selects it works fine ?
>> #2 0x00007f11c1800e24 in sqlitefdw_report_error (elevel=<value optimized >> out> , stmt=0x20013f8, conn=<value optimized out>, sql=0x0, rc=1) at >> connection.c:288
This is a bug in sqlite_fdw - it's assuming it can use sqlite3_sql to get the sql source text back from a statement, but that's only true when the statement was prepared using a different API than the one actually being used. So sqlite3_sql ends up returning null, and pstrdup naturally crashes on that.
