RE: BUG #19411: libpq 16.x exhibits a memory leak when connections are repeatedly created and destroyed

From: Matt Carter <Matt(dot)Carter(at)twosigma(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: RE: BUG #19411: libpq 16.x exhibits a memory leak when connections are repeatedly created and destroyed
Date: 2026-02-17 23:12:15
Message-ID: BL3PR08MB72834BCE3E34DB8BFB24ED61996DA@BL3PR08MB7283.namprd08.prod.outlook.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Matt Carter wrote:
> Tom, since your C test showed no leak, the issue is likely in how psycopg2 calls libpq, not pure libpq itself.

FYI, I have reported the issue to the psycopg project:
https://github.com/psycopg/psycopg2/issues/1827

Thanks you for your help, Tom. Your test results helped show that this is likely a psycopg2 issue.

Cheers,
Matt

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Richard Guo 2026-02-18 01:51:40 Re: BUG #19412: Wrong query result with not null constraint
Previous Message David Rowley 2026-02-17 22:53:50 Re: BUG #19412: Wrong query result with not null constraint