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

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 15:23:50
Message-ID: CAG3yVS7NDzT4vBWvuVs7Z5KL5Un=u-w-od1a+9APqSaamN1jwg@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.
>

Interesting!
Do you run pg_repack on a regular schedule using something like cron, or
does it run automatically in the background?
Is it compatible with PostgreSQL 9.6?

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Nicolas Grilly 2016-08-31 15:33:18 Re: Clustered index to preserve data locality in a multitenant application?
Previous Message Salvatore Tomaselli 2016-08-31 14:38:13 BDR: Transactions with global lock