Re[2]: [BUGS] Re[2]: [BUGS] Segfault in MemoryContextAlloc - Mailing list pgsql-bugs

From Dmitriy Sarafannikov
Subject Re[2]: [BUGS] Re[2]: [BUGS] Segfault in MemoryContextAlloc
Date
Msg-id 1455021299.648137543@f28.i.mail.ru
Whole thread Raw
In response to Re: Re[2]: [BUGS] Segfault in MemoryContextAlloc  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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

pgsql-bugs by date:

Previous
From: Michael Paquier
Date:
Subject: Re: BUG #13916: Only the install user can be defined in the new cluster
Next
From: Andrew Dunstan
Date:
Subject: Re: BUG #13936: jsonb_object() -> ERROR: unknown type of jsonb container