pgsql: Avoid core dump in _outPathInfo() for Path without a parent RelO

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Avoid core dump in _outPathInfo() for Path without a parent RelO
Date: 2014-10-18 02:33:58
Message-ID: E1XfJqA-0006Ej-Sj@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Avoid core dump in _outPathInfo() for Path without a parent RelOptInfo.

Nearly all Paths have parents, but a ResultPath representing an empty FROM
clause does not. Avoid a core dump in such cases. I believe this is only
a hazard for debugging usage, not for production, else we'd have heard
about it before. Nonetheless, back-patch to 9.1 where the troublesome code
was introduced. Noted while poking at bug #11703.

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/5ba062ee44c35b4dc49ccf869fe48f3c6f5f926f

Modified Files
--------------
src/backend/nodes/outfuncs.c | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2014-10-18 02:55:56 pgsql: Declare mkdtemp() only if we're providing it.
Previous Message Tom Lane 2014-10-18 02:33:44 pgsql: Avoid core dump in _outPathInfo() for Path without a parent RelO