Re: ERROR's turning FATAL in BRIN regression tests

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: John Naylor <jcnaylor(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: ERROR's turning FATAL in BRIN regression tests
Date: 2018-10-19 14:19:44
Message-ID: 32398.1539958784@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

John Naylor <jcnaylor(at)gmail(dot)com> writes:
> I changed the signature of a freespace.c function that the BRIN code
> calls, and this change by itself doesn't cause a crash. With the full
> FSM patch, causing BRIN errors in manual queries in psql doesn't cause
> a crash. However, during the BRIN regression tests, the queries that
> purposely cause errors result in FATAL instead, causing a crash.

Sounds like something's messing up the backend's exception stack,
so that elog.c has noplace to throw the error to. See the
promote-ERROR-to-FATAL logic therein.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Adrian Klaver 2018-10-19 14:31:24 Re: Problem about partitioned table
Previous Message Michael Paquier 2018-10-19 14:07:31 Re: WAL archive (archive_mode = always) ?