| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | "hirose(dot)masay-01(at)fujitsu(dot)com" <hirose(dot)masay-01(at)fujitsu(dot)com> |
| Cc: | 'Tom Lane' <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #17421: Core dump in ECPGdo() when calling PostgreSQL API from 32-bit client for RHEL8 |
| Date: | 2022-03-05 10:29:23 |
| Message-ID: | YiM7gxu7cxarLUc4@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Sat, Mar 05, 2022 at 06:45:21AM +0000, hirose(dot)masay-01(at)fujitsu(dot)com wrote:
> My test case to reproduce the issue is:
> 1. The client connects Postgres Database and issues SQL continuously.
> 2. Switch the Database role from Active to Standby.
> The Database is mirrored by the Mirroring Controller between two
> clustered servers. the Mirroring Controller may be the original
> feature added by the enterprise.
A self-contained test case enters in the category of an ECPG script
that we could use to reproduce the problem. Personally, I have no
idea what kind of application stack you are using, and I don't know
TJVvDatabaseAPI, which I suspect is a proprietary solution for
something related to databases. The information you are providing
here is not enough for one to know how to reproduce this problem.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2022-03-05 15:19:02 | Re: BUG #17421: Core dump in ECPGdo() when calling PostgreSQL API from 32-bit client for RHEL8 |
| Previous Message | hirose.masay-01@fujitsu.com | 2022-03-05 06:45:21 | RE: BUG #17421: Core dump in ECPGdo() when calling PostgreSQL API from 32-bit client for RHEL8 |