| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Julien Rouhaud <julien(dot)rouhaud(at)dalibo(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: segfault in HEAD when too many nested functions call |
| Date: | 2017-07-18 20:43:59 |
| Message-ID: | 6325.1500410639@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andres Freund <andres(at)anarazel(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-07-18 20:53:43 | Re: segfault in HEAD when too many nested functions call |
| Previous Message | Andres Freund | 2017-07-18 20:04:10 | Re: segfault in HEAD when too many nested functions call |