| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alexander Lakhin <exclusion(at)gmail(dot)com> |
| Cc: | Peter Geoghegan <pg(at)bowt(dot)ie>, 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:47 |
| Message-ID: | 2155320.1682913887@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Alexander Lakhin <exclusion(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2023-05-01 04:04:56 | Re: BUG #17798: Incorrect memory access occurs when using BEFORE ROW UPDATE trigger |
| Previous Message | Alexander Lakhin | 2023-05-01 04:00:00 | Re: BUG #17798: Incorrect memory access occurs when using BEFORE ROW UPDATE trigger |