Re: Clustered index to preserve data locality in a multitenant application?

Поиск
Список
Период
Сортировка
От Nicolas Grilly
Тема Re: Clustered index to preserve data locality in a multitenant application?
Дата
Msg-id CAG3yVS5zM97YdwMK5y7NU-vYATnrx89DAQg5kR=sPzV1CmRTog@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Clustered index to preserve data locality in a multitenant application?  (Kenneth Marshall <ktm@rice.edu>)
Ответы Re: Clustered index to preserve data locality in a multitenant application?  (Ben Chobot <bench@silentmedia.com>)
Список pgsql-general
Дерево обсуждения
On Tue, Aug 30, 2016 at 8:17 PM, Kenneth Marshall <ktm@rice.edu> wrote:
We have been using the extension pg_repack to keep a table groomed into
cluster order. With an appropriate FILLFACTOR to keep updates on the same
page, it works well. The issue is that it needs space to rebuild the new
index/table. If you have that, it works well.

It looks like Instagram has been using pg_reorg (the ancestor of pg_repack) to keep all likes from the same user contiguous on disk, in order to minimize disk seeks.

http://instagram-engineering.tumblr.com/post/40781627982/handling-growth-with-postgres-5-tips-from

This is very similar to what I'm trying to achieve.

The article is 3 years old. I'd be curious to know if they still do that.

Nicolas

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

Предыдущее
От: Kenneth Marshall
Дата:
Сообщение: Re: Clustered index to preserve data locality in a multitenant application?
Следующее
От: Ben Chobot
Дата:
Сообщение: Re: Clustered index to preserve data locality in a multitenant application?