| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| 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:55:50 |
| Message-ID: | CAB7nPqT=cj06jkmbXf6uVbCZWTZWKw-NEWg5GNUXu4Kij7VekQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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?
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2017-08-08 19:57:47 | Re: signal 11 segfaults with parallel workers |
| Previous Message | Andres Freund | 2017-08-08 19:51:19 | Re: signal 11 segfaults with parallel workers |