Re: errbacktrace

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Dmitry Dolgov <9erthalion6(at)gmail(dot)com>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Subject: Re: errbacktrace
Date: 2019-11-23 16:14:06
Message-ID: 20191123161406.GA8050@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On 2019-Nov-23, Tom Lane wrote:

> I had occasion to try to use errbacktrace() just now, and it blew up
> on me. Investigation finds this:
> int
> errbacktrace(void)
> {
> ErrorData *edata = &errordata[errordata_stack_depth];
> MemoryContext oldcontext;
> Assert(false);
> I suppose that's a debugging leftover that shouldn't have been committed?
> It did what I wanted after I took out the Assert.

Uhh ... facepalm. Yes, that's not intended. I don't remember why would
I want to put that there.

Álvaro Herrera
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2019-11-23 16:34:45 XID-wraparound hazards in LISTEN/NOTIFY
Previous Message Tom Lane 2019-11-23 16:11:08 Re: errbacktrace