Message-ID: <486f389c-9306-23db-dbb5-5ffc3fec411d@enterprisedb.com>
Date: Wed, 9 Aug 2023 17:56:48 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
 Thunderbird/102.13.0
Subject: Re: pgsql: Ignore BRIN indexes when checking for HOT udpates
To: Alvaro Herrera <alvherre@alvh.no-ip.org>,
 pgsql-hackers@lists.postgresql.org
Cc: Matthias van de Meent <boekewurm+postgres@gmail.com>,
 Tomas Vondra <tomas.vondra@postgresql.org>,
 =?UTF-8?B?Sm9zZWYgxaBpbcOhbmVr?= <josef.simanek@gmail.com>
References: <20230809091155.7c7f3gttjk3dj4ze@alvherre.pgsql>
Content-Language: en-US
From: Tomas Vondra <tomas.vondra@enterprisedb.com>
In-Reply-To: <20230809091155.7c7f3gttjk3dj4ze@alvherre.pgsql>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/486f389c-9306-23db-dbb5-5ffc3fec411d%40enterprisedb.com>
Precedence: bulk

On 8/9/23 11:11, Alvaro Herrera wrote:
> On 2021-Nov-30, Tomas Vondra wrote:
> 
>> Ignore BRIN indexes when checking for HOT udpates
> 
> I was trying to use RelationGetIndexAttrBitmap for something and
> realized that its header comment does not really explain things very
> well.  That was already the case before this commit, but it (this
> commit) did add new possible values without mentioning them.  I propose
> the attached comment-only patch.
> 

+1

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