Re: MVCC overheads

Поиск
Список
Период
Сортировка
От Alvaro Herrera
Тема Re: MVCC overheads
Дата
Msg-id 20160708174654.GA730281@alvherre.pgsql
обсуждение исходный текст
Ответ на Re: MVCC overheads  (Pete Stevenson <etep.nosnevets@gmail.com>)
Ответы Re: MVCC overheads  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
Pete Stevenson wrote:

> Maybe I could figure out the lines of code that add versions into a
> table and then those that collect old versions (they do get collected,
> right?). Anyway, thought being I could profile while running TPC-C or
> similar. I was hoping that someone might be able to jump on this with
> a response that they already did something similar.

Old tuple versions are "collected" (removed) by either vacuum (see
vacuumlazy.c) and heap_page_prune.  The latter is one thing that could
perhaps somehow be offloaded, as it's quite independent from the other
stuff.  You can prune removable tuples at no additional cost from an
unlocked dirty page, which is a useful optimization because then
client-connected backends don't need to prune them later.

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



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

Предыдущее
От: Fabien COELHO
Дата:
Сообщение: Re: minor plpgsql doc patch
Следующее
От: Andres Freund
Дата:
Сообщение: Re: Re: [COMMITTERS] pgsql: Avoid extra locks in GetSnapshotData if old_snapshot_threshold <