Re: Segmentation Fault in Postgres server when using psqlODBC

From: Joshua Berry <yoberi(at)gmail(dot)com>
To: "Inoue, Hiroshi" <inoue(at)tpf(dot)co(dot)jp>
Cc: pgsql-odbc(at)postgresql(dot)org
Subject: Re: Segmentation Fault in Postgres server when using psqlODBC
Date: 2013-06-04 15:48:33
Message-ID: CAPmZXM08s=6=owEWsu542QSz6ME8McpoA8RwGwSJQHDNS-v5TA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-odbc

Hi Hiroshi,

On Tue, Jun 4, 2013 at 9:46 AM, Joshua Berry <yoberi(at)gmail(dot)com> wrote:

>
> On Mon, Jun 3, 2013 at 10:47 PM, Inoue, Hiroshi <inoue(at)tpf(dot)co(dot)jp> wrote:
>
>> It's also preferrable to fix the crash at backend.
>> The crash is caused by execute commands after commit.
>>
>
> That would be the best solution. Thanks for your help.
>

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.

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?

Kind Regards,
-Joshua

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2013-06-04 17:53:03 Re: Memory-leak in BackgroundWriter(and Checkpointer)
Previous Message Federico Campoli 2013-06-04 15:36:53 Re: BUG #8192: On very large tables the concurrent update with vacuum lag the hot_standby replica

Browse pgsql-odbc by date

  From Date Subject
Next Message Marco Gaiarin 2013-06-05 13:25:09 Upgrade strangeness on win 32bit
Previous Message Joshua Berry 2013-06-04 14:46:39 Re: Segmentation Fault in Postgres server when using psqlODBC