Hi,
>Seems some basic mistake I think it should as below
>(*param_types)[i] = exprType(param_expr);
>
>After this it works
Seems to work fine from my side.
Thank you very much, it'd painful for me to find the bug, I've been too far
away from C coding for a too long time :-(
--
Hervé LEFEBVRE
On Tue, Nov 20, 2018 at 7:59 PM Tomas Vondra
wrote:
>
> On 11/20/18 3:06 PM, 066ce...@free.fr wrote:
> > Hi,
> >
> >> When gdb will be active, then use command c, and then run query in
> >> session. gdb should to catch segfault.
> >
> > Thank you very much. It's been helpfull.
> >
> > BTW behavio
066ce...@free.fr writes:
> What is confusing, is that if I do the same with a pl/pgsql function (see
> below) I can run it 5 times, and the 6th exec hit the same SEGV...
That probably reflects switching from a custom plan to a generic plan
on the sixth execution.
regards,
On 11/20/18 3:06 PM, 066ce...@free.fr wrote:
Hi,
When gdb will be active, then use command c, and then run query in session. gdb
should to catch segfault.
Thank you very much. It's been helpfull.
BTW behaviour is strange. When I'm executing following, I do have always a SEGV
:
psql (11.1)
Hi,
>When gdb will be active, then use command c, and then run query in session.
>gdb should to catch segfault.
Thank you very much. It's been helpfull.
BTW behaviour is strange. When I'm executing following, I do have always a SEGV
:
psql (11.1)
Type "help" for help.
herve=# CREATE OR R
Hi
út 20. 11. 2018 v 11:09 odesílatel <066ce...@free.fr> napsal:
> Hi,
>
> I do have a reproductible crash with mysql_fdw when executing a plpgsql
> function. I'm running pg 11.1 with current mysql_fdw, but I had the same
> crash with the pg 9.6 and mysql_fdw provided with ubuntu packages.
>
> Fr
