| From: | Dmitriy Sarafannikov <dimon99901(at)mail(dot)ru> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, pgsql-bugs <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re[2]: [BUGS] Re[2]: [BUGS] Segfault in MemoryContextAlloc |
| Date: | 2016-02-09 12:34:59 |
| Message-ID: | 1455021299.648137543@f28.i.mail.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
>Both this and the other behavior you reported sure seem like "can't
>happen" situations. I do have a theory though: I think you are doing
>something that is spawning multiple threads inside the backend, and then
>the backend logic goes nuts because it's expecting to be single-threaded.
>
>pg_buffercache wouldn't do that, and a quick google search suggests that
>V8 knows nothing of threads either. Have you got anything else going
>on in there?
No, we don't use anything except sql, plv8 and plpgsql.
it is also sometimes crashes on simplest queries like select 'ping'.
Is it possible that some signal handler resets the TopTransactionContext to NULL?
--
Best regards,
Dmitriy Sarafannikov
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2016-02-09 12:38:07 | Re: Re: BUG #13685: Archiving while idle every archive_timeout with wal_level hot_standby |
| Previous Message | Michael Paquier | 2016-02-09 12:03:36 | Re: BUG #13916: Only the install user can be defined in the new cluster |