Horton
Menu

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

Tom Lane <tgl@sss.pgh.pa.us>

View thread
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Tomas Vondra <tomas.vondra@enterprisedb.com>
Cc: Justin Pryzby <pryzby@telsasoft.com>, Josef Šimánek <josef.simanek@gmail.com>, Alvaro Herrera <alvherre@alvh.no-ip.org>, pgsql-hackers@postgresql.org
Date: 2021-12-06T01:47:30Z
Lists: pgsql-hackers 
Tomas Vondra <tomas.vondra@enterprisedb.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

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Ignore BRIN indexes when checking for HOT updates

  2. Move test for BRIN HOT behavior to stats.sql

  3. Ignore BRIN indexes when checking for HOT udpates