Feedback-ID: ia2694551:Fastmail
Date: Wed, 9 Aug 2023 11:11:55 +0200
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: pgsql-hackers@lists.postgresql.org
Cc: Matthias van de Meent <boekewurm+postgres@gmail.com>,
	Tomas Vondra <tomas.vondra@postgresql.org>,
	Josef =?utf-8?B?xaBpbcOhbmVr?= <josef.simanek@gmail.com>
Subject: Re: pgsql: Ignore BRIN indexes when checking for HOT udpates
Message-ID: <20230809091155.7c7f3gttjk3dj4ze@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="sr6mye444zs4xrf5"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <E1ms8Qp-0007re-JL@gemulon.postgresql.org>
Archived-At: 
 <https://www.postgresql.org/message-id/20230809091155.7c7f3gttjk3dj4ze%40alvherre.pgsql>
Precedence: bulk


--sr6mye444zs4xrf5
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit

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.

-- 
Álvaro Herrera               48°01'N 7°57'E  —  https://www.EnterpriseDB.com/
Al principio era UNIX, y UNIX habló y dijo: "Hello world\n".
No dijo "Hello New Jersey\n", ni "Hello USA\n".

--sr6mye444zs4xrf5
Content-Type: text/x-diff; charset=us-ascii
Content-Disposition: attachment;
	filename="0001-Document-RelationGetIndexAttrBitmap-better.patch"