From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alexander Lakhin <exclusion@gmail.com>
cc: Peter Geoghegan <pg@bowt.ie>, pgsql-bugs@lists.postgresql.org,
        Richard Guo <guofenglinux@gmail.com>,
        Andres Freund <andres@anarazel.de>
Subject: Re: BUG #17798: Incorrect memory access occurs when using BEFORE ROW
 UPDATE trigger
In-reply-to: <88b5750f-a5da-798b-e5a1-af2c3ecb9b60@gmail.com>
References: <17798-0907404928dcf0dd@postgresql.org>
 <87fe6c28-80b2-f709-a8db-d105e5240e39@gmail.com>
 <CAMbWs4_pg7ab=OJF2CGLzs=noWEjujerxfo92sm3RL9ce=ogsQ@mail.gmail.com>
 <CAMbWs48FHhuuuWbxygO4Wey7ahdaSwRjzJODKXx7=GFsge_aLg@mail.gmail.com>
 <f5ff446f-72e2-44f7-80c6-4256cf7caeb3@gmail.com>
 <a4a8cf37-e9d5-3c58-fc2e-d217cf66f315@gmail.com>
 <1849610.1682807087@sss.pgh.pa.us>
 <bc6d1314-4e7a-2bde-1f01-a14de4909efd@gmail.com>
 <CAH2-Wzm3aQznsDrVu10C3hcvez8qwdy2578Hw4BgwXLWZ1NDQw@mail.gmail.com>
 <88b5750f-a5da-798b-e5a1-af2c3ecb9b60@gmail.com>
Comments: In-reply-to Alexander Lakhin <exclusion@gmail.com>
	message dated "Mon, 01 May 2023 07:00:00 +0300"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2155319.1682913887.1@sss.pgh.pa.us>
Date: Mon, 01 May 2023 00:04:47 -0400
Message-ID: <2155320.1682913887@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/2155320.1682913887%40sss.pgh.pa.us>
Precedence: bulk

Alexander Lakhin <exclusion@gmail.com> writes:
> So I'm going to start it over and find a repro that will show something
> interesting without Valgrind (and let estimate the probability of a
> problem in the field).

I think a probability estimate is not all that exciting: "it's low
but not zero" is sufficient information to act on.  What I am curious
about is how come 86dc90056's changes triggered a visible problem.
Understanding that might give us a better feel for what is the real
structural issue here --- which I'm worried about because I have
little confidence that there aren't similar bugs lurking in other
code paths.

			regards, tom lane