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

From: Nicolas Grilly <nicolas(at)gardentechno(dot)com>
To: Ben Chobot <bench(at)silentmedia(dot)com>
Cc: 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:25:44
Message-ID: CAG3yVS7jn6qhBL0iwroiqW3MPx1=nE3tL8Di=V5tt8N8qt2tsA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, Sep 1, 2016 at 12:05 AM, Ben Chobot <bench(at)silentmedia(dot)com> wrote:

> If what they did 3 years ago is similar to what you are trying to do
> today, who cares what they are doing today? (Besides using pg_repack
> instead of pg_reorg, of course.)
>

I'm curious because, in the meantime, Instagram could have stopped doing
this because 1) it didn't work as intended or 2) they found a better
solution.

> For what it's worth, we use pg_repack on a regular basis and it works
> exactly as advertised.
>

Thanks.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Nicolas Grilly 2016-08-31 22:31:49 Re: Clustered index to preserve data locality in a multitenant application?
Previous Message Ben Chobot 2016-08-31 22:05:11 Re: Clustered index to preserve data locality in a multitenant application?