Re: BUG #17798: Incorrect memory access occurs when using BEFORE ROW UPDATE trigger

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Alexander Lakhin <exclusion(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)lists(dot)postgresql(dot)org, Richard Guo <guofenglinux(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>
Subject: Re: BUG #17798: Incorrect memory access occurs when using BEFORE ROW UPDATE trigger
Date: 2023-05-01 04:04:56
Message-ID: CAH2-Wznc0qLvPXNiDCHnN59P8_9mttia8m2uqpaUPrVrPxcByA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Sun, Apr 30, 2023 at 9:00 PM Alexander Lakhin <exclusion(at)gmail(dot)com> wrote:
> Yes, I am. That's why I can't demonstrate real risks now — my repro
> triggers a Valgrind warning only, and no other consequences are visible.

It would be nice to be able to say something about the severity with
high confidence, but this seems like the kind of thing that rarely
goes that way. Does it really matter? A bug is a bug.

--
Peter Geoghegan

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message David Rowley 2023-05-01 04:40:52 Re: BUG #17913: alter column set (n_distinct=...) on partition head doesn't work for declarative partitioned tables
Previous Message Tom Lane 2023-05-01 04:04:47 Re: BUG #17798: Incorrect memory access occurs when using BEFORE ROW UPDATE trigger