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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>
Cc: Justin Pryzby <pryzby(at)telsasoft(dot)com>, 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 01:47:30
Message-ID: 2982546.1638755250@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com> writes:
> On 12/5/21 21:16, Tom Lane wrote:
>> 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.

Another idea, perhaps, is to shove that test into stats.sql,
where people would know to ignore it? (Actually, I've thought
more than once that we should mark stats.sql as ignorable
in the schedule ...)

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2021-12-06 02:30:17 Re: MSVC SSL test failure
Previous Message Euler Taveira 2021-12-06 01:19:27 Re: row filtering for logical replication