Re: BUG #16801: Invalid memory access on WITH RECURSIVE with nested WITHs

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>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #16801: Invalid memory access on WITH RECURSIVE with nested WITHs
Date: 2021-02-25 03:12:07
Message-ID: YDcVh8R7OArj9dtV@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, Feb 24, 2021 at 09:48:03PM -0500, Tom Lane wrote:
> Anyway, I think we're better off with a test that doesn't require
> DEBUG_LIST_MEMORY_USAGE, or preferably not even CLOBBER_FREED_MEMORY,
> to show the problem. The test I showed misbehaves even in non-debug
> builds, because it actually depends on what's in the innerwiths lists.

Yeah. What I sent previously does not break in non-debug builds, but
it does with just --enable-cassert.

Hmm. I'd like to think that this would be enough for this thread, and
I cannot come up now with a test able to break the lists for non-debug
builds. But perhaps you have an idea?
--
Michael

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message wangsh.fnst@fujitsu.com 2021-02-25 06:07:06 RE: BUG #15858: could not stat file - over 4GB
Previous Message Tom Lane 2021-02-25 02:48:03 Re: BUG #16801: Invalid memory access on WITH RECURSIVE with nested WITHs