Re: BUG #18135: Incorrect memory access occurs when attaching a partition with an index

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Alexander Lakhin <exclusion(at)gmail(dot)com>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18135: Incorrect memory access occurs when attaching a partition with an index
Date: 2023-09-28 07:07:35
Message-ID: ZRUmN-ma7f_w2CeU@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, Sep 28, 2023 at 08:00:00AM +0300, Alexander Lakhin wrote:
> Please try the following procedure (I've simplified my own):
> With the attached patch (for HEAD) applied
> CPPFLAGS="-DUSE_VALGRIND "

USE_VALGRIND is the difference here. In the past problems with
valgrind I've seen from you, I've never needed that, actually.

In my case, my process is much simpler: I just use installcheck with
an instance I set up locally using a command like the one I mentioned
above. No need to patch the tree with that and self-contained SQL
sequences.

Anyway, mystery solved.
--
Michael

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Michael Paquier 2023-09-28 07:16:47 Re: BUG #18127: Assertion HaveRegisteredOrActiveSnapshot failed on REINDEX CONCURRENTLY when blocksize=1
Previous Message Andrey Lepikhov 2023-09-28 06:32:25 Re: EXPLAIN Verbose issue - custom_scan_tlist can directly refer CTE and Subquery