Postgres Pro
Downloads
Home   >   mailing lists

Re: terminate called after throwing an instance of 'std::bad_alloc' - Mailing list pgsql-hackers

From Tom Lane
Subject Re: terminate called after throwing an instance of 'std::bad_alloc'
Date
Msg-id 951178.1601518842@sss.pgh.pa.us
Whole thread Raw
In response to terminate called after throwing an instance of 'std::bad_alloc'  (Justin Pryzby <pryzby@telsasoft.com>)
List pgsql-hackers
Tree view 
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

pgsql-hackers by date:

Previous
From: Kyotaro Horiguchi
Date:
Subject: Re: Asynchronous Append on postgres_fdw nodes.
Next
From: James Coleman
Date:
Subject: Re: enable_incremental_sort changes query behavior