From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: jora.gevorgyan@rau.am
Subject: BUG #18338: Memory leak in function 'dumpRule'
Date: Mon, 12 Feb 2024 13:36:13 +0000
Message-ID: <18338-ddb9deb8f1646d01@postgresql.org> (raw)
The following bug has been logged on the website:
Bug reference: 18338
Logged by: Jora
Email address: jora.gevorgyan@rau.am
PostgreSQL version: 16.2
Operating system: Ubuntu 20.04
Description:
The memory leak is found by a static analyzer developed at [CAST](
https://www.linkedin.com/company/cast-center/).
The memory alocated at [in qtabname]() is getting lost when function
[pg_fatal is
called](https://github.com/postgres/postgres/blob/09eb633e1baa3b7cd7929f3cc77f9c46f63c20b1/src/bin/pg_dump/p...)
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, jora.gevorgyan@rau.am
Subject: Re: BUG #18338: Memory leak in function 'dumpRule'
In-Reply-To: <18338-ddb9deb8f1646d01@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