Re: Multiple FPI_FOR_HINT for the same block during killing btree index items

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: James Coleman <jtc331(at)gmail(dot)com>
Cc: Masahiko Sawada <masahiko(dot)sawada(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Álvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Subject: Re: Multiple FPI_FOR_HINT for the same block during killing btree index items
Date: 2020-04-10 00:32:22
Message-ID: CAH2-Wzm-Pf2xKR2mfk55s88_8RGXix2VJH4R0Wmk7=YwVuH19Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Apr 9, 2020 at 5:25 PM Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
> Was this a low cardinality index in the way I describe? If it was,
> then we can hope (and maybe even verify) that the Postgres 12 work
> noticeably ameliorates the problem.

What I really meant was an index where hundreds or even thousands of
rows for each distinct timestamp value are expected. Not an index
where almost every row has a distinct timestamp value. Both timestamp
index patterns are common, obviously.

--
Peter Geoghegan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2020-04-10 01:20:10 Re: Catalog invalidations vs catalog scans vs ScanPgRelation()
Previous Message Peter Geoghegan 2020-04-10 00:25:08 Re: Multiple FPI_FOR_HINT for the same block during killing btree index items