On 3/9/22 12:41, Amit Kapila wrote: > On Wed, Mar 9, 2022 at 4:14 AM Tomas Vondra > <tomas.von...@enterprisedb.com> wrote: >> >> On 3/7/22 22:11, Tomas Vondra wrote: >>> >>> I've pushed this simple fix. Not sure it'll fix the assert failures on >>> skink/locust, though. Given the lack of information it'll be difficult >>> to verify. So let's wait a bit. >>> >> >> I've done about 5000 runs of 'make check' in test_decoding, on two rpi >> machines (one armv7, one aarch64). Not a single assert failure :-( >> >> How come skink/locust hit that in just a couple runs? >> > > Is it failed after you pushed a fix? I don't think so or am I missing > something? I feel even if doesn't occur again it would have been > better if we had some theory on how it occurred in the first place > because that would make us feel more confident that we won't have any > related problem left. >
I don't think it failed yet - we have to wait a bit longer to make any conclusions, though. On skink it failed only twice over 1 month. I agree it'd be nice to have some theory, but I really don't have one. regards -- Tomas Vondra EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
