| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | exclusion(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #16801: Invalid memory access on WITH RECURSIVE with nested WITHs |
| Date: | 2021-01-03 05:15:58 |
| Message-ID: | X/FTDocQD3D7+aIJ@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Sat, Jan 02, 2021 at 03:00:00PM +0000, PG Bug reporting form wrote:
> valgrind detects an invalid read:
> ==00:00:00:04.145 217144== Invalid read of size 8
> ==00:00:00:04.145 217144== at 0x302CB7: makeDependencyGraphWalker
> (parse_cte.c:549)
> ==00:00:00:04.145 217144== by 0x302EA1: makeDependencyGraph
> (parse_cte.c:439)
> ==00:00:00:04.145 217144== by 0x304557: transformWithClause
> (parse_cte.c:176)
>
> The first bad commit is 1cff1b95.
The same kind of list manipulation is done in two places in
parse_cte.c, and there are extra ones in split_pathtarget_walker(). I
cannot reproduce that here, and I have just tried with different
optimization levels on HEAD and REL_13_STABLE. Are you using specific
options for valgrind?
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Lakhin | 2021-01-03 06:00:00 | Re: BUG #16801: Invalid memory access on WITH RECURSIVE with nested WITHs |
| Previous Message | PG Bug reporting form | 2021-01-02 15:00:00 | BUG #16801: Invalid memory access on WITH RECURSIVE with nested WITHs |