From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: 1157401338@qq.com
Subject: BUG #17632: a potential bug of memory leak
Date: Tue, 11 Oct 2022 02:33:34 +0000
Message-ID: <17632-bd589e2276faf5d0@postgresql.org> (raw)
The following bug has been logged on the website:
Bug reference: 17632
Logged by: a potential bug of memory leak
Email address: 1157401338@qq.com
PostgreSQL version: 14.5
Operating system: ubuntu20.04
Description:
Hi, I found a potential memory leak bug in the project source
code of postgre, and I have shown the execution sequence of the program
that
may generate the bug on a graph,which can be access by
https://docimg8.docs.qq.com/image/AgAACEPRUipmYhhKHB5OOoBr8hpUfqC5.png?w=2192&h=1336
The red text illustrates the steps that generate the bug,,the file path can
be seen in the blue framed
section.
Although the code shown is for version 12.12 but is still exist in current
version
would you can help to check if this bug is true?thank you for your effort
and patience!
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: noreply@postgresql.org, pgsql-bugs@lists.postgresql.org, 1157401338@qq.com
Subject: Re: BUG #17632: a potential bug of memory leak
In-Reply-To: <17632-bd589e2276faf5d0@postgresql.org>
* 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