From: Michael Paquier <michael@paquier.xyz>
To: Alexander Lakhin <exclusion@gmail.com>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18135: Incorrect memory access occurs when attaching a partition with an index
Date: Thu, 28 Sep 2023 16:07:35 +0900
Message-ID: <ZRUmN-ma7f_w2CeU@paquier.xyz> (raw)
In-Reply-To: <9e3acda6-76b8-d6b4-c013-f78f84d7c5ab@gmail.com>
References: <18135-532f4a755e71e4d2@postgresql.org>
<ZRTzX0h68fxZ5Dth@paquier.xyz>
<9e3acda6-76b8-d6b4-c013-f78f84d7c5ab@gmail.com>
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
Attachments:
signature.asc (application/pgp-signature, 832B) download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: michael@paquier.xyz, exclusion@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18135: Incorrect memory access occurs when attaching a partition with an index
In-Reply-To: <ZRUmN-ma7f_w2CeU@paquier.xyz>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox