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:
Inoue, Hiroshi <in...@tpf.co.jp <mailto:in...@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.
>
>
> I'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?
>>
>
> Oops it's an Execute message used in extended query protocol not a
> *EXECUTE* command.
>
printtup_holdable_cursor.patch
Description: Binary data
-- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
