Re: BUG #18135: Incorrect memory access occurs when attaching a partition with an index - Mailing list pgsql-bugs

From Alexander Lakhin
Subject Re: BUG #18135: Incorrect memory access occurs when attaching a partition with an index
Date
Msg-id 9a80e4e9-2c07-2d0f-4447-b98c0d51e540@gmail.com
Whole thread Raw
In response to Re: BUG #18135: Incorrect memory access occurs when attaching a partition with an index  (Michael Paquier <michael@paquier.xyz>)
List pgsql-bugs
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



pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #18137: PG16 release note doc bug in "Allow GRANT group_name TO user_name ..."
Next
From: Marek Malevič
Date:
Subject: Broken type checking for empty subqueries