Postgres Pro
Downloads
Home   >   mailing lists

Re: Multiple FPI_FOR_HINT for the same block during killing btreeindex items - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: Multiple FPI_FOR_HINT for the same block during killing btreeindex items
Date
Msg-id CAH2-Wzm2BPMD0JFVgUtpC-YGM6zjrwJJ6ixYOCSKr8QNoNuz3g@mail.gmail.com
Whole thread Raw
In response to Re: Multiple FPI_FOR_HINT for the same block during killing btreeindex items  (James Coleman <jtc331@gmail.com>)
Responses Re: Multiple FPI_FOR_HINT for the same block during killing btreeindex items  (James Coleman <jtc331@gmail.com>)
List pgsql-hackers
Tree view 
On Thu, Apr 9, 2020 at 6:47 PM James Coleman <jtc331@gmail.com> wrote:
> I believe the write pattern to this table likely looks like:
> - INSERT
> - UPDATE
> - DELETE
> for every row. But tomorrow I can do some more digging if needed.

The pg_stats.null_frac for the column/index might be interesting here. I
believe that Active Record will sometimes generate created_at columns
that sometimes end up containing NULL values. Not sure why.


--
Peter Geoghegan

pgsql-hackers by date:

Previous
From: James Coleman
Date:
Subject: Re: Multiple FPI_FOR_HINT for the same block during killing btreeindex items
Next
From: Fujii Masao
Date:
Subject: Re: [HACKERS] make async slave to wait for lsn to be replayed