| 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:52:41 |
| Message-ID: | CAG3yVS78Pytg8i=0FbPe_q=Ypa7kXfOWqyioxB7mq6kPVYfFKA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Sep 1, 2016 at 12:31 AM, Nicolas Grilly <nicolas(at)gardentechno(dot)com>
wrote:
> 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?
>
I forgot the links to DB2 documentation about clustering index:
http://www.ibm.com/support/knowledgecenter/SSEPEK_10.0.0/intro/src/tpc/db2z_clusteringindexes.html
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adam Brusselback | 2016-08-31 23:24:05 | Re: Vacuum Full - Questions |
| Previous Message | Patrick B | 2016-08-31 22:41:27 | Rackspace to RDS using DMS (Postgres 9.2) |