From: Tomas Vondra <tomas@vondra.me>
To: Abhishek Mittal <abhmittal@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Junwang Zhao <zhjwpku@gmail.com>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18624: Memory Leak Issue with PostgreSQL Connection During COPY Command Execution.
Date: Thu, 3 Oct 2024 14:30:19 +0200
Message-ID: <e37eb66f-be10-49fa-95dc-253dea622685@vondra.me> (raw)
In-Reply-To: <CAEHmedC7KFNceNn97qDAagMr_e1G2+ckZZtKcKmQeSbFZAajfA@mail.gmail.com>
References: <18624-451f53141608af60@postgresql.org>
<CAEG8a3Kb+SNKKW_q6qV+ah3FRyW4omujjzXDo3rJ-xB2w=+z7Q@mail.gmail.com>
<CAEHmedAb2d-2uYnKbcqDAMrP9Suw1VoOLqcP8rcsef6H8-DiMQ@mail.gmail.com>
<2466048.1726854902@sss.pgh.pa.us>
<CAEHmedAi11b4T6-gvVU-FKwJaFv3CZGPqsjy5Szxy58D4HW9mA@mail.gmail.com>
<CAEHmedC7KFNceNn97qDAagMr_e1G2+ckZZtKcKmQeSbFZAajfA@mail.gmail.com>
On 10/3/24 11:49, Abhishek Mittal wrote:
> Hi,
>
> I'm currently facing a blocker in my project. Could we please check this
> issue.
>
> Thank you for your assistance.
>
Please, don't top post. Reply in-line.
You have not reported if you tried upgrading to 12.20. Chances are this
issue was already fixed since 12.16, people are unlikely to spend time
investigating this, only to find it was a waste of time.
Also, Tom asked you a couple important questions you ignored:
> 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?
Please provide this info. It was suggested to try with "jit=off", so
maybe try that too - I personally don't see why would that matter for
the COPY command, but maybe it does ...
Finally, I wonder if you're simply misinterpreting what RES means. It's
not "private memory used by the process". So if you're simply seeing RES
to grow to 10GB and conclude "memory leak", it may not be the case. It
could be shared memory, for example - you need to inspect "smaps" for
the process to see what exactly the RES figure includes.
regards
--
Tomas Vondra
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: tomas@vondra.me, abhmittal@gmail.com, tgl@sss.pgh.pa.us, 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: <e37eb66f-be10-49fa-95dc-253dea622685@vondra.me>
* 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