From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Rick Otten <rottenwindfish(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org>, ronan(dot)dunklau(at)dalibo(dot)com |
Subject: | Re: signal 11 segfaults with parallel workers |
Date: | 2017-07-31 07:52:40 |
Message-ID: | CAB7nPqSa4p+tVpfXRHoV-Ex2DA46SzYNdNoa+GXCWvSz=x3G8w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Mon, Jul 31, 2017 at 5:41 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> writes:
>> There is already a "Parallel Worker" memory context defined by that
>> time. I think the issue is that multicorn library expects that
>> Transaction context to be defined by that time.
>
> It looks like multicorn supposes that a library's _PG_init function can
> only be called inside a transaction. That is broken with a capital B.
> We need not consider parallel query to find counterexamples: that
> means you can't preload multicorn using shared_preload_libraries,
> as that loads libraries into the postmaster, which never has and never
> will run transactions.
>
> Whatever it's trying to initialize in _PG_init needs to be done later.
Indeed, that's bad. I am adding in CC Ronan who has been working on
multicorn. At this stage, I think that you would be better out by
disabling parallelism.
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Daniel Verite | 2017-07-31 16:21:44 | Crash report for some ICU-52 (debian8) COLLATE and work_mem values |
Previous Message | Tom Lane | 2017-07-31 03:41:21 | Re: signal 11 segfaults with parallel workers |