| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Peter Geoghegan <pg(at)bowt(dot)ie>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #16036: Segmentation fault while doing an update |
| Date: | 2019-10-05 16:26:59 |
| Message-ID: | 20191005162659.dl3ajuvxcjxlvb3d@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Hi,
On 2019-10-05 11:30:39 -0400, Tom Lane wrote:
> Andres Freund <andres(at)anarazel(dot)de> writes:
> > I've now disabled that portion of the test.
>
> There's still a large fraction of the buildfarm that's unhappy :-(
I pushed a second patch disabling two more permutations, I've not seen
any related failures since. It's frustrating that we at the moment seem
to not have deterministic behaviour with two sessions waiting for a
tuple lock at the moment. Doesn't look like that's new though.
It seems to me that most of the XactLockTableWait() users ought to
follow the pattern outlined at the top of README.tuplock, but
don't.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-10-05 16:28:01 | Re: BUG #16042: incorrect .gitignore file |
| Previous Message | Tom Lane | 2019-10-05 15:30:39 | Re: BUG #16036: Segmentation fault while doing an update |