| From: | Nicolas Grilly <nicolas(at)gardentechno(dot)com> |
|---|---|
| To: | Kenneth Marshall <ktm(at)rice(dot)edu> |
| Cc: | Vick Khera <vivek(at)khera(dot)org>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Clustered index to preserve data locality in a multitenant application? |
| Date: | 2016-08-31 22:31:49 |
| Message-ID: | CAG3yVS5mW6R7F9N-W1NrthZBRGEhOgmtYTLsVHqXWgANXkntrg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Aug 30, 2016 at 8:17 PM, Kenneth Marshall <ktm(at)rice(dot)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?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Patrick B | 2016-08-31 22:41:25 | Vacuum Full - Questions |
| Previous Message | Nicolas Grilly | 2016-08-31 22:25:44 | Re: Clustered index to preserve data locality in a multitenant application? |