Re: BUG #18624: Memory Leak Issue with PostgreSQL Connection During COPY Command Execution.
От | Abhishek Mittal |
---|---|
Тема | Re: BUG #18624: Memory Leak Issue with PostgreSQL Connection During COPY Command Execution. |
Дата | |
Msg-id | CAEHmedC7KFNceNn97qDAagMr_e1G2+ckZZtKcKmQeSbFZAajfA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: BUG #18624: Memory Leak Issue with PostgreSQL Connection During COPY Command Execution. (Abhishek Mittal <abhmittal@gmail.com>) |
Ответы |
Re: BUG #18624: Memory Leak Issue with PostgreSQL Connection During COPY Command Execution.
|
Список | pgsql-bugs |
Hi,
I'm currently facing a blocker in my project. Could we please check this issue.
Thank you for your assistance.
Thank you for your assistance.
Regards
Abhishek Mitta
On Tue, Sep 24, 2024 at 11:15 AM Abhishek Mittal <abhmittal@gmail.com> wrote:
Hi,Thanks for your response.Can we connect sometime over the call to see the issue in my environment..RegardsAbhishek MittalOn Fri, Sep 20, 2024 at 11:25 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:Abhishek Mittal <abhmittal@gmail.com> writes:
> Please find the table schema below along with the attached sample CSV file.
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 Gustafsson)
If that's it, then setting "jit = 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--amittal
amittal
В списке pgsql-bugs по дате отправления: