| From: | Kenneth Marshall <ktm(at)rice(dot)edu> |
|---|---|
| To: | Nicolas Grilly <nicolas(at)gardentechno(dot)com> |
| 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 16:05:20 |
| Message-ID: | 20160831160520.GF4950@aart.rice.edu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Aug 31, 2016 at 05:23:50PM +0200, Nicolas Grilly wrote:
> 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?
Hi,
We just run it via cron. In our case, we run it once a day, but depending on
your churn, it could be run once a week or more.
Regards,
Ken
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nicolas Grilly | 2016-08-31 16:06:54 | Re: Clustered index to preserve data locality in a multitenant application? |
| Previous Message | Nicolas Grilly | 2016-08-31 15:40:51 | Re: Clustered index to preserve data locality in a multitenant application? |