pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  

help / color / mirror / Atom feed
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
Date: Mon, 06 May 2024 10:41:11 -0400
Message-ID: <3592572.1715006471@sss.pgh.pa.us> (raw)
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>

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/





view thread (5+ messages)

Message-ID: <3592572.1715006471@sss.pgh.pa.us>
Permalink:  ../3592572.1715006471@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/3592572.1715006471@sss.pgh.pa.us

 · 

reply
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: tgl@sss.pgh.pa.us, jacques@quantsolutions.co.za, 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: <3592572.1715006471@sss.pgh.pa.us>

* 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