From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
Cc: Julien Rouhaud <julien.rouhaud@dalibo.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: segfault in HEAD when too many nested functions call
Date: Tue, 18 Jul 2017 16:43:59 -0400
Message-ID: <6325.1500410639@sss.pgh.pa.us> (raw)
In-Reply-To: <20170718200410.254wlnzpmzxwskor@alap3.anarazel.de>
References: <b0af9eaa-130c-60d0-9e4e-7a135b1e0c76@dalibo.com>
<12302.1500132157@sss.pgh.pa.us>
<20170717072629.dqykbsot2irdob7c@alap3.anarazel.de>
<20170717145710.cm32m4yn555hsoxd@alap3.anarazel.de>
<3979.1500407153@sss.pgh.pa.us>
<20170718200410.254wlnzpmzxwskor@alap3.anarazel.de>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
Andres Freund <andres@anarazel.de> writes:
> On 2017-07-18 15:45:53 -0400, Tom Lane wrote:
>> While I'm uncomfortable with making such a change post-beta2, I'm one
>> heck of a lot *more* uncomfortable with shipping v10 with no stack depth
>> checks in the executor mainline. Fleshing this out and putting it in
>> v10 might be an acceptable compromise.
> Ok, I'll flesh out the patch till Thursday. But I do think we're going
> to have to do something about the back branches, too.
I'm not worried about the back branches. The stack depth checks have
been in those same places for ten years at least, and there are no field
reports of trouble.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, andres@anarazel.de, julien.rouhaud@dalibo.com
Subject: Re: segfault in HEAD when too many nested functions call
In-Reply-To: <6325.1500410639@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox