From: Alexander Lakhin <exclusion@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-bugs@lists.postgresql.org, Richard Guo <guofenglinux@gmail.com>
Subject: Re: BUG #17798: Incorrect memory access occurs when using BEFORE ROW UPDATE trigger
Date: Sat, 29 Apr 2023 12:00:00 +0300
Message-ID: <a4a8cf37-e9d5-3c58-fc2e-d217cf66f315@gmail.com> (raw)
In-Reply-To: <f5ff446f-72e2-44f7-80c6-4256cf7caeb3@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>
Hello Tom,
20.04.2023 13:00, Alexander Lakhin wrote:
>
> 19.04.2023 11:29, Richard Guo wrote:
>> I have a second look at this issue and now I think the fix in v1 patch
>> is correct. I think the comment needs to be updated for this change,
>> maybe something like
>>
>
> I've updated the comment based on your suggestion. Please look at the patch
> attached.
>
Could you please confirm the issue, Richard's and my conclusions, and the
correctness of the patch, in light of the upcoming May releases?
Maybe I'm wrong, but I think that this bug can lead to data corruption in
databases where BRU triggers are used.
If the defect is real, but the patch proposed is not good enough, I would
register it on the commitfest to continue working on it.
Best regards,
Alexander
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: exclusion@gmail.com, tgl@sss.pgh.pa.us, guofenglinux@gmail.com
Subject: Re: BUG #17798: Incorrect memory access occurs when using BEFORE ROW UPDATE trigger
In-Reply-To: <a4a8cf37-e9d5-3c58-fc2e-d217cf66f315@gmail.com>
* 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