| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Dmitriy Sarafannikov <dimon99901(at)mail(dot)ru> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, pgsql-bugs <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: Re[2]: [BUGS] Segfault in MemoryContextAlloc |
| Date: | 2016-02-06 23:37:58 |
| Message-ID: | 31612.1454801878@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
=?UTF-8?B?RG1pdHJpeSBTYXJhZmFubmlrb3Y=?= <dimon99901(at)mail(dot)ru> writes:
>> That's, uh, weird. TopTransactionContext should never be NULL here. This
>> is with a stock 9.4.5, without any further extensions configured?
> It is a stock 9.4.5 with pg_buffercache (1.0) and plv8 (1.4.0) installed extensions.
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?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2016-02-07 00:19:08 | Re: Re: BUG #13685: Archiving while idle every archive_timeout with wal_level hot_standby |
| Previous Message | Tom Lane | 2016-02-06 23:30:20 | Re: Re[2]: [BUGS] Segfault in MemoryContextAlloc |