Message-ID: <9a80e4e9-2c07-2d0f-4447-b98c0d51e540@gmail.com>
Date: Thu, 28 Sep 2023 11:00:00 +0300
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
 Thunderbird/102.4.2
Subject: Re: BUG #18135: Incorrect memory access occurs when attaching a
 partition with an index
Content-Language: en-US
To: Michael Paquier <michael@paquier.xyz>
Cc: pgsql-bugs@lists.postgresql.org
References: <18135-532f4a755e71e4d2@postgresql.org>
 <ZRTzX0h68fxZ5Dth@paquier.xyz>
 <9e3acda6-76b8-d6b4-c013-f78f84d7c5ab@gmail.com>
 <ZRUmN-ma7f_w2CeU@paquier.xyz>
From: Alexander Lakhin <exclusion@gmail.com>
In-Reply-To: <ZRUmN-ma7f_w2CeU@paquier.xyz>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/9a80e4e9-2c07-2d0f-4447-b98c0d51e540%40gmail.com>
Precedence: bulk

28.09.2023 10:07, Michael Paquier wrote:
> 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.

Yes, I know that method, but unfortunately it doesn't cover TAP tests,
so I prefer to use such patch to perform whole check-world (and run also all
postgres binaries, e.g., pg_dump) under valgrind.

As to patching regress/sql/, in this case my intention was to minimize the
self-contained repro. I use separate scripts for running arbitrary SQL,
for sure.

Best regards,
Alexander