From: Tom Lane <tgl@sss.pgh.pa.us>
To: Sudheer H R <sudheer.hr@tekenlight.com>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: Memory leakage in libpq valgrind test
Date: Wed, 01 Mar 2023 01:43:50 -0500
Message-ID: <1327895.1677653030@sss.pgh.pa.us> (raw)
In-Reply-To: <D0C58678-5E88-40E7-8611-510F89367F69@tekenlight.com>
References: <D0C58678-5E88-40E7-8611-510F89367F69@tekenlight.com>
Sudheer H R <sudheer.hr@tekenlight.com> writes:
> While running valgrind to detect memory leaks, found the following as one of the leaks.
> Request you to comment on this.
So ... why do you think this is our bug, and not a Kerberos bug?
The leak seems to be buried quite far in libgssapi_krb5.so.
regards, tom lane
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: tgl@sss.pgh.pa.us, sudheer.hr@tekenlight.com, pgsql-bugs@lists.postgresql.org
Subject: Re: Memory leakage in libpq valgrind test
In-Reply-To: <1327895.1677653030@sss.pgh.pa.us>
* 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