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 | CAG3yVS5mW6R7F9N-W1NrthZBRGEhOgmtYTLsVHqXWgANXkntrg@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?
Re: Clustered index to preserve data locality in a multitenant application? |
| Список | 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.
In DB2, it seems possible to define a "clustering index" that determines how rows are physically ordered in the "table space" (the heap).
The documentation says: "When a table has a clustering index, an INSERT statement causes DB2 to insert the records as nearly as possible in the order of their index values."
It looks like a kind of "continuous CLUSTER/pg_repack". Is there something similar available or planned for PostgreSQL?
В списке pgsql-general по дате отправления: