From: Tom Lane <tgl@sss.pgh.pa.us>
To: Abhishek Mittal <abhmittal@gmail.com>
cc: Junwang Zhao <zhjwpku@gmail.com>, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18624: Memory Leak Issue with PostgreSQL Connection During
 COPY Command Execution.
In-reply-to: 
 <CAEHmedAb2d-2uYnKbcqDAMrP9Suw1VoOLqcP8rcsef6H8-DiMQ@mail.gmail.com>
References: <18624-451f53141608af60@postgresql.org>
 <CAEG8a3Kb+SNKKW_q6qV+ah3FRyW4omujjzXDo3rJ-xB2w=+z7Q@mail.gmail.com>
 <CAEHmedAb2d-2uYnKbcqDAMrP9Suw1VoOLqcP8rcsef6H8-DiMQ@mail.gmail.com>
Comments: In-reply-to Abhishek Mittal <abhmittal@gmail.com>
	message dated "Thu, 19 Sep 2024 16:34:01 +0530"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2466047.1726854902.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Fri, 20 Sep 2024 13:55:02 -0400
Message-ID: <2466048.1726854902@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/2466048.1726854902%40sss.pgh.pa.us>
Precedence: bulk

Abhishek Mittal <abhmittal@gmail.com> writes:
> Please find the table schema below along with the attached sample CSV fi=
le.

I too tried to reproduce this, using both Junwang's \gexec method
and the C program.  I don't see any leak.  However, I tested v12
branch tip, so it's possible that you are hitting a problem that's
been fixed since 12.16.  I notice a plausibly-related item in the
12.18 release notes:

	Fix memory leak when performing JIT inlining (Andres Freund, Daniel Gusta=
fsson)

If that's it, then setting "jit =3D off" should do as a temporary
workaround.

If updating to 12.20 does not resolve the problem, then we are
going to need more information.  Is this straight community
Postgres, or some variant?  If you built it yourself, what
options did you use?  Do you have any extensions installed?

			regards, tom lane