Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps
 (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1mGi39-0002Hd-7Z
	for pgsql-bugs@arkaria.postgresql.org; Thu, 19 Aug 2021 13:25:39 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1mGi38-0004u8-7y
	for pgsql-bugs@arkaria.postgresql.org; Thu, 19 Aug 2021 13:25:38 +0000
Received: from makus.postgresql.org ([2001:4800:3e1:1::229])
	by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <demurgos@demurgos.net>)
	id 1mGhlp-00024l-Sl
	for pgsql-bugs@lists.postgresql.org; Thu, 19 Aug 2021 13:07:45 +0000
Received: from out2.migadu.com ([2001:41d0:2:aacc::])
	by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <demurgos@demurgos.net>)
	id 1mGhll-0002Hi-Pu
	for pgsql-bugs@lists.postgresql.org; Thu, 19 Aug 2021 13:07:44 +0000
Subject: Re: BUG #17053: Memory corruption in parser on prepared query reuse
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=demurgos.net;
	s=default; t=1629378457;
	h=from:from:reply-to:subject:subject:date:date:message-id:message-id:
	 to:to:cc:cc:mime-version:mime-version:content-type:content-type:
	 content-transfer-encoding:content-transfer-encoding:
	 in-reply-to:in-reply-to:references:references;
	bh=LlmF+33fpZJdAUbVkGrFIxWpZWVAxnDz11xmQpNAscA=;
	b=Igw1IpKA3S9g2Dtj4fru+7zJGn+RGWDDhd2MZhMABCNd4Y+VhzqSma+A+jAvcGe7Vf2dyy
	ulafTGmnPZAJDjUt9+HQ1MnCu10ALvjg1poNYeSDJ+ZLzGecELyyis8Gqsi0U09P1F1RAw
	KBU+gy5SULj2KLxMUKefsquVngamxDA=
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-bugs@lists.postgresql.org
References: <17053-3ca3f501bbc212b4@postgresql.org>
 <1509789.1623274896@sss.pgh.pa.us>
X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and
 include these headers.
From: Charles Samborski <demurgos@demurgos.net>
Message-ID: <832b765a-e974-ca1e-06f0-28af3c8877c7@demurgos.net>
Date: Thu, 19 Aug 2021 15:07:35 +0200
MIME-Version: 1.0
In-Reply-To: <1509789.1623274896@sss.pgh.pa.us>
Content-Type: text/plain; charset=windows-1252
Content-Language: fr
Content-Transfer-Encoding: 7bit
X-Migadu-Flow: FLOW_OUT
X-Migadu-Auth-User: demurgos@demurgos.net
List-Id: <pgsql-bugs.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-bugs@lists.postgresql.org>
List-Owner: <mailto:pgsql-bugs-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-bugs>
Archived-At: 
 <https://www.postgresql.org/message-id/832b765a-e974-ca1e-06f0-28af3c8877c7%40demurgos.net>
Precedence: bulk

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