Re: sqlite_fdw crashes & errors

From: Mariel Cherkassky <mariel(dot)cherkassky(at)gmail(dot)com>
To: andrew(at)tao11(dot)riddles(dot)org(dot)uk
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:17:09
Message-ID: CA+t6e1kZNsdLw6bRhhzKrjDsr784sES_FErb-5dXhi5EJKoD7Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)tao11(dot)riddles(dot)org(dot)uk‬‏>:‬

> >>>>> "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)
>

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Andrew Gierth 2018-09-18 13:33:41 Re: sqlite_fdw crashes & errors
Previous Message Andrew Gierth 2018-09-18 13:12:46 Re: sqlite_fdw crashes & errors