Re: sqlite_fdw crashes & errors
| От | Mariel Cherkassky |
|---|---|
| Тема | Re: sqlite_fdw crashes & errors |
| Дата | |
| Msg-id | CA+t6e1kZNsdLw6bRhhzKrjDsr784sES_FErb-5dXhi5EJKoD7Q@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: sqlite_fdw crashes & errors (Andrew Gierth <andrew@tao11.riddles.org.uk>) |
| Ответы |
Re: sqlite_fdw crashes & errors
|
| Список | pgsql-admin |
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 ?
בתאריך יום ג׳, 18 בספט׳ 2018 ב-16:13 מאת Andrew Gierth <andrew@tao11.riddles.org.uk>:
>>>>> "Mariel" == Mariel Cherkassky <mariel.cherkassky@gmail.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)
В списке pgsql-admin по дате отправления: