| From: | PG Bug reporting form <noreply(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Cc: | 1157401338(at)qq(dot)com |
| Subject: | BUG #17632: a potential bug of memory leak |
| Date: | 2022-10-11 02:33:34 |
| Message-ID: | 17632-bd589e2276faf5d0@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 17632
Logged by: a potential bug of memory leak
Email address: 1157401338(at)qq(dot)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!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kyotaro Horiguchi | 2022-10-11 06:48:24 | Re: Startup process on a hot standby crashes with an error "invalid memory alloc request size 1073741824" while replaying "Standby/LOCK" records |
| Previous Message | Tom Lane | 2022-10-10 20:53:28 | Re: BUG #17631: Prepare + Merge fails to identify parameter types |
