Re: terminate called after throwing an instance of 'std::bad_alloc'
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Justin Pryzby <pryzby@telsasoft.com>
Cc: pgsql-hackers@postgresql.org, Andres Freund <andres@anarazel.de>
Date: 2020-10-01T02:20:42Z
Lists: pgsql-hackers
Justin Pryzby <pryzby@telsasoft.com> writes: > A VM crashed which is now running PG13.0 on centos7: > Sep 30 19:40:08 database7 abrt-hook-ccpp: Process 17905 (postgres) of user 26 killed by SIGABRT - dumping core > Core was generated by `postgres: telsasoft ts 192.168.122.11(34608) SELECT '. > Unfortunately, the filesystem wasn't large enough and the corefile is > truncated. Hm, can you fix that? A stack trace would be mighty handy here. regards, tom lane
Commits
-
llvmjit: Use explicit LLVMContextRef for inlining
- 3b991f81c457 12.18 landed
- 10912f7d4ff0 13.14 landed
- 75a20a4b4b44 14.11 landed
- aef521849b68 15.6 landed
- 2cf50585e54a 16.2 landed
- 9dce22033d5d 17.0 landed