| From: | Aleksander Alekseev <aleksander(at)timescale(dot)com> |
|---|---|
| To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Cc: | Yasir <yasir(dot)hussain(dot)shah(at)gmail(dot)com> |
| Subject: | Re: Valgrind - showing memory leaks? |
| Date: | 2025-05-08 12:20:49 |
| Message-ID: | CAJ7c6TN3Xk9_MAuJqgtLfNZTP0bZJUWYbPkMcoFhuBwSADTM7g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi Yasir
> I ran a postgres server with valgrind looking for memory leaks at a particular extension, but I am experiencing something strange. Here are the steps:
> [...]
> 5. Question:
> ----------------
> I believe that the valgrind should not report any memory leaks in such simple/common commands. What am I doing wrong here?
Out-of-the box Valgrind is not aware of the concept of MemoryContexts
in Postgres. If nothing has changed in recent years you should open
src/include/pg_config_manual.h and make sure it has:
```
#define USE_VALGRIND
```
Then rebuild Postgres and run your tests again. Please let us know the results.
--
Best regards,
Aleksander Alekseev
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aleksander Alekseev | 2025-05-08 12:22:35 | Re: [PATCH] oauth: Prevent stack overflow by limiting JSON parse depth |
| Previous Message | Daniel Gustafsson | 2025-05-08 11:20:06 | Re: disabled SSL log_like tests |