Re: [PATCH] Don't block HOT update by BRIN index

From: Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Justin Pryzby <pryzby(at)telsasoft(dot)com>
Cc: Josef Šimánek <josef(dot)simanek(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [PATCH] Don't block HOT update by BRIN index
Date: 2021-12-06 00:51:47
Message-ID: d57873f2-f05a-2c74-d1b6-b0e702f7ecec@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 12/5/21 21:16, Tom Lane wrote:
> Justin Pryzby <pryzby(at)telsasoft(dot)com> writes:
>> brin.sql's new brin_hot test is failing sometimes.
>> Evidently because:
>> | 2021-12-01 04:02:01.096 CET [61a6e587.3106b1:4] LOG: wait_for_hot_stats delayed 33.217301 seconds
>> It seems like maybe the UDP packet lost to the stats collector got lost ?
>> It fails less than 10% of the time here, probably depending on load.
>
> Oh, geez. *Please* let us not add another regression failure mode
> like the ones that afflict stats.sql. We do not need a doubling
> of that failure rate. I suggest just removing this test.
>

Whooops. Agreed, I'll get rid of that test.

regards

--
Tomas Vondra
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kyotaro Horiguchi 2021-12-06 00:56:20 Re: Is ssl_crl_file "SSL server cert revocation list"?
Previous Message Tom Lane 2021-12-06 00:41:14 Re: pg_dump versus ancient server versions