Re: Clustered index to preserve data locality in a multitenant application? - Mailing list pgsql-general

From Nicolas Grilly
Subject Re: Clustered index to preserve data locality in a multitenant application?
Date
Msg-id CAG3yVS7NDzT4vBWvuVs7Z5KL5Un=u-w-od1a+9APqSaamN1jwg@mail.gmail.com
Whole thread Raw
In response to Re: Clustered index to preserve data locality in a multitenant application?  (Kenneth Marshall <ktm@rice.edu>)
Responses Re: Clustered index to preserve data locality in a multitenant application?  (Kenneth Marshall <ktm@rice.edu>)
List 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.

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?

pgsql-general by date:

Previous
From: "Karl O. Pinc"
Date:
Subject: postgresql.conf RH comment, and a systemd RH note
Next
From: Nicolas Grilly
Date:
Subject: Re: Clustered index to preserve data locality in a multitenant application?