From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: wizardbrony@gmail.com
Subject: BUG #18512: Backend memory leak when using command parameters after generating notifications
Date: Sun, 16 Jun 2024 20:18:32 +0000
Message-ID: <18512-6e89f654d7da884d@postgresql.org> (raw)
The following bug has been logged on the website:
Bug reference: 18512
Logged by: Wiz
Email address: wizardbrony@gmail.com
PostgreSQL version: 14.7
Operating system: Windows 10
Description:
All the details for this issue were originally reported to the GitHub
project for the database driver I use (Npgsql), but it was concluded that
the problem is in Postgres itself. Here is a link to that page:
https://github.com/npgsql/npgsql/issues/5703
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, wizardbrony@gmail.com
Subject: Re: BUG #18512: Backend memory leak when using command parameters after generating notifications
In-Reply-To: <18512-6e89f654d7da884d@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