| From: | Роман Хапов <r(dot)khapov(at)yandex(dot)ru> |
|---|---|
| To: | Daniel Gustafsson <daniel(at)yesql(dot)se>, "m(dot)korotkov(at)postgrespro(dot)ru" <m(dot)korotkov(at)postgrespro(dot)ru> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_dump: fix memory leak |
| Date: | 2025-08-29 07:31:21 |
| Message-ID: | 325051756452526@mail.yandex.ru |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
<div> </div><blockquote><p><br />This is not actually a leak since the application will terminate immediately if<br />a restrict key cannot be generated.</p></blockquote><div> </div><div>Seems like this will silence static analyzer and help to find real problems in reduced warning/errors list.</div><div> </div><div>--</div><div>Roman Khapov</div>
| Attachment | Content-Type | Size |
|---|---|---|
| unknown_filename | text/html | 355 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | m.korotkov | 2025-08-29 07:36:22 | Re: pg_dump: fix memory leak |
| Previous Message | Pavel Stehule | 2025-08-29 07:27:36 | Re: pgbench: extend variable usage in scripts |