Re: [ODBC] Segmentation Fault in Postgres server when using psqlODBC
От | Joshua Berry |
---|---|
Тема | Re: [ODBC] Segmentation Fault in Postgres server when using psqlODBC |
Дата | |
Msg-id | CAPmZXM0ye9i3ib+pXoimf6C6GpGUgdKbvydUFFg2+VQyj+u-6Q@mail.gmail.com обсуждение исходный текст |
Ответ на | Segmentation Fault in Postgres server when using psqlODBC (Joshua Berry <yoberi@gmail.com>) |
Ответы |
Re: [ODBC] Segmentation Fault in Postgres server when using
psqlODBC
|
Список | pgsql-bugs |
Hiroshi Inoue has developed the attached patch to correct the issue that was reported. More of the dialogue can be found in the pgsql-odbc list.
The root issue:
The root issue:
Inoue, Hiroshi <inoue@tpf.co.jp <mailto:inoue@tpf.co.jp>> wrote:
It's also preferrable to fix the crash at backend.
The crash is caused by execute commands after commit.
Regarding testing:
Is there any test code that I could leverage to put together a test case
which can quickly invoke the backend problem that I'm seeing? Perhaps
something that is used in the pgsqlODBC project or something else you or others might have sitting around? I would like to have a
testapp/function that could help verify that the issue has been fixed in
a future backend patch/release.
It seems difficult to provide a test code. However I can reproduce
the crash by changing 1 line of psqlodbc driver source code with a
test case. For example, the crash is fixed by the attached patch.Oops it's an Execute message used in extended query protocol not aI've never explicitly used EXECUTE. Could I construct a plpgsql script
which could use EXECUTE in a similar manner as psqlODBC, thus creating a
test case that would have greater portability?
*EXECUTE* command.
Вложения
В списке pgsql-bugs по дате отправления: