| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Cc: | 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> |
| Subject: | Re: signal 11 segfaults with parallel workers |
| Date: | 2017-07-31 03:41:21 |
| Message-ID: | 694.1501472481@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2017-07-31 07:52:40 | Re: signal 11 segfaults with parallel workers |
| Previous Message | Amit Kapila | 2017-07-31 03:22:44 | Re: signal 11 segfaults with parallel workers |