Re: [BUGS] signal 11 segfaults with parallel workers - Mailing list pgsql-bugs

From Tom Lane
Subject Re: [BUGS] signal 11 segfaults with parallel workers
Date
Msg-id 694.1501472481@sss.pgh.pa.us
Whole thread Raw
In response to Re: [BUGS] signal 11 segfaults with parallel workers  (Amit Kapila <amit.kapila16@gmail.com>)
Responses Re: [BUGS] signal 11 segfaults with parallel workers  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-bugs
Amit Kapila <amit.kapila16@gmail.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.
        regards, tom lane


-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

pgsql-bugs by date:

Previous
From: Amit Kapila
Date:
Subject: Re: [BUGS] signal 11 segfaults with parallel workers
Next
From: Michael Paquier
Date:
Subject: Re: [BUGS] signal 11 segfaults with parallel workers