Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1s3zWq-00HCE4-Ff
	for pgsql-bugs@arkaria.postgresql.org; Mon, 06 May 2024 14:41:20 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.94.2)
	(envelope-from <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1s3zWn-00DbI6-7R
	for pgsql-bugs@arkaria.postgresql.org; Mon, 06 May 2024 14:41:18 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1s3zWm-00DbHy-VM
	for pgsql-bugs@lists.postgresql.org; Mon, 06 May 2024 14:41:17 +0000
Received: from sss.pgh.pa.us ([68.162.161.243])
	by magus.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1s3zWk-001rA4-Mb
	for pgsql-bugs@lists.postgresql.org; Mon, 06 May 2024 14:41:17 +0000
Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 446EfBg73592573;
	Mon, 6 May 2024 10:41:12 -0400
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jacques Combrink <jacques@quantsolutions.co.za>
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18456: Trigger data in plpython3u trigger-function changes
 in AFTER UPDATE OR INSERT trigger
In-reply-to: 
 <CAO2Kw=fU9qa48Gj9-OKCwBUEGZAtUm+UDT=Sb+EPjroxmEC8Vw@mail.gmail.com>
References: <18456-82d3d70134aefd28@postgresql.org>
 <2944262.1714847680@sss.pgh.pa.us>
 <CAO2Kw=fU9qa48Gj9-OKCwBUEGZAtUm+UDT=Sb+EPjroxmEC8Vw@mail.gmail.com>
Comments: In-reply-to Jacques Combrink <jacques@quantsolutions.co.za>
	message dated "Mon, 06 May 2024 10:23:24 +0200"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3592571.1715006471.1@sss.pgh.pa.us>
Date: Mon, 06 May 2024 10:41:11 -0400
Message-ID: <3592572.1715006471@sss.pgh.pa.us>
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/3592572.1715006471%40sss.pgh.pa.us>
Precedence: bulk

Jacques Combrink <jacques@quantsolutions.co.za> writes:
> Okay thanks for confirming.
> Is there something that I can do to get this issue on a list to be fixed,
> or is this report enough?

The patch is already queued [1].  It's a bit too late for this week's
releases, but it'll be in 17beta1 and in the August quarterly
releases.

			regards, tom lane

[1] https://commitfest.postgresql.org/48/4970/