| From: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> |
|---|---|
| To: | Mariel Cherkassky <mariel(dot)cherkassky(at)gmail(dot)com> |
| Cc: | mark(dot)kirkwood(at)catalyst(dot)net(dot)nz, pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | Re: sqlite_fdw crashes & errors |
| Date: | 2018-09-18 13:12:46 |
| Message-ID: | 87sh27hrxj.fsf@news-spur.riddles.org.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
>>>>> "Mariel" == Mariel Cherkassky <mariel(dot)cherkassky(at)gmail(dot)com> writes:
>> #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.
--
Andrew (irc:RhodiumToad)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mariel Cherkassky | 2018-09-18 13:17:09 | Re: sqlite_fdw crashes & errors |
| Previous Message | Mariel Cherkassky | 2018-09-18 12:35:11 | Re: sqlite_fdw crashes & errors |