Re: Multiple FPI_FOR_HINT for the same block during killing btreeindex items

Поиск
Список
Период
Сортировка
От James Coleman
Тема Re: Multiple FPI_FOR_HINT for the same block during killing btreeindex items
Дата
Msg-id CAAaqYe8ku-_Hj6SP=S9FWKEbb+Kj6BGWKT2d=fr_FW8Jx62RDA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Multiple FPI_FOR_HINT for the same block during killing btreeindex items  (Peter Geoghegan <pg@bowt.ie>)
Список pgsql-hackers
On Thu, Apr 9, 2020 at 10:08 PM Peter Geoghegan <pg@bowt.ie> wrote:
>
> 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.

null_frac is 0 for created_at (what I expected). Also (under current
data) all created_at values are unique except a single row duplicate.

That being said, remember the write pattern above: every row gets
deleted eventually, so there'd be a lots of dead tuples overall.

James



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Robert Haas
Дата:
Сообщение: Re: Improve heavyweight locks instead of building new lock managers?
Следующее
От: Jeremy Morton
Дата:
Сообщение: Re: Support for DATETIMEOFFSET