Re: terminate called after throwing an instance of 'std::bad_alloc'

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Justin Pryzby <pryzby(at)telsasoft(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org, Andres Freund <andres(at)anarazel(dot)de>
Subject: Re: terminate called after throwing an instance of 'std::bad_alloc'
Date: 2020-10-01 02:20:42
Message-ID: 951178.1601518842@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Justin Pryzby <pryzby(at)telsasoft(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message James Coleman 2020-10-01 02:21:37 Re: enable_incremental_sort changes query behavior
Previous Message Kyotaro Horiguchi 2020-10-01 02:16:53 Re: Asynchronous Append on postgres_fdw nodes.