From: Tom Lane <tgl@sss.pgh.pa.us>
To: d.kovalenko@postgrespro.ru
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18983: Problems with Postgres "make check" under ASAN
In-reply-to: <18983-92ece795f4630781@postgresql.org>
References: <18983-92ece795f4630781@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Wed, 09 Jul 2025 17:19:19 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1334079.1752085555.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Wed, 09 Jul 2025 14:25:55 -0400
Message-ID: <1334080.1752085555@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1334080.1752085555%40sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.org> writes:
> We want testing our components and extensions for Postgres under ASAN bu=
t
> the problems within original PG code does not allow to do it easily.
> I won't describe each detected problems but provide these things:
> 1) Link to clone of the current master source that is able to pass "make
> check"
> https://github.com/dmitry-lipetsk/postgres/commits/D20250709_001--memory=
_leaks--master/

We do not accept patch submissions in this way.  Please email a patch
file to the pgsql-hackers list.

FWIW, if this is mostly about memory leaks, there's already work
in progress at

https://www.postgresql.org/message-id/flat/285483.1746756246@sss.pgh.pa.us

			regards, tom lane