| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Alexander Lakhin <exclusion(at)gmail(dot)com>, zuming(dot)jiang(at)inf(dot)ethz(dot)ch, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #17995: Segmentation fault caused by UPDATE statement |
| Date: | 2023-06-26 04:56:42 |
| Message-ID: | ZJkais2u82EUwD24@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Mon, Jun 26, 2023 at 12:27:08AM -0400, Tom Lane wrote:
> Michael Paquier <michael(at)paquier(dot)xyz> writes:
>> Thanks for the pointer, I'll double-check that. Some of the locations
>> of stack depth checks proposed involve performance-sensitive code
>> paths, though, like mcxt.c :/
>
> I hadn't looked at the patch yet, but ... mcxt.c? How is that recursive?
> Even if there is some path that recurses through that, wouldn't the
> check be better placed in a less-hot part of the loop?
Yeah, that's my impression. I'll switch to the other thread after
looking more in details.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Lakhin | 2023-06-26 05:00:01 | Re: BUG #17995: Segmentation fault caused by UPDATE statement |
| Previous Message | Amit Kapila | 2023-06-26 04:42:30 | Re: BUG #17993: FK issue on logical replication table |