From: Charles Samborski <demurgos@demurgos.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17053: Memory corruption in parser on prepared query reuse
Date: Thu, 19 Aug 2021 15:07:35 +0200
Message-ID: <832b765a-e974-ca1e-06f0-28af3c8877c7@demurgos.net> (raw)
In-Reply-To: <1509789.1623274896@sss.pgh.pa.us>
References: <17053-3ca3f501bbc212b4@postgresql.org>
<1509789.1623274896@sss.pgh.pa.us>
I am not familiar with how Postgres tracks its bugs. How can I check the
status of this bug #17053? Is it still pending?
> The attached patch seems to fix it. I wonder though if we ought to
> move the copying to someplace more centralized. I cannot escape the
> suspicion that there are more of these creepy-crawlies in other
> poorly-tested utility statements.
Is the quick-fix already applied or do you want to wait for these
larger changes? I was hoping to drop my workarounds once the fixes for
this bug land.
Regards,
Charles Samborski
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: demurgos@demurgos.net, tgl@sss.pgh.pa.us, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17053: Memory corruption in parser on prepared query reuse
In-Reply-To: <832b765a-e974-ca1e-06f0-28af3c8877c7@demurgos.net>
* 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