| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
| Cc: | Rick Otten <rottenwindfish(at)gmail(dot)com>, ronan(dot)dunklau(at)dalibo(dot)com, PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Subject: | Re: signal 11 segfaults with parallel workers |
| Date: | 2017-08-08 19:57:47 |
| Message-ID: | 20170808195747.4ki4gzxkqimbev6m@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 2017-08-08 21:55:50 +0200, Michael Paquier wrote:
> On Tue, Aug 8, 2017 at 9:51 PM, Andres Freund <andres(at)anarazel(dot)de> wrote:
> > Perhaps, for v11, we should actually make sure there's no memory context
> > etc set during _PG_init() to catch such problems earlier? It's a bit
> > nasty to only see them if the shared library is preloaded and/or
> > parallelism is in use.
>
> Yeah, some prevention like that would be a good idea for module
> developers.
> We could also check for a higher-level thing like being sure that
> there is no transaction context?
Not quite sure what you mean by that? And if you just mean to ensure
that _PG_init() is called outside of a transaction - how? We load shared
libraries on demand when they're used - and that'll frequently be in a
transaction?
- Andres
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-08-08 20:15:15 | |
| Previous Message | Michael Paquier | 2017-08-08 19:55:50 | Re: signal 11 segfaults with parallel workers |