vacuum vs pg_repack for clearing bloat? - Mailing list pgsql-general

From Lists
Subject vacuum vs pg_repack for clearing bloat?
Date
Msg-id 52D72338.4070908@benjamindsmith.com
Whole thread Raw
Responses Re: vacuum vs pg_repack for clearing bloat?  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: vacuum vs pg_repack for clearing bloat?  (Andrew Sullivan <ajs@crankycanuck.ca>)
Re: vacuum vs pg_repack for clearing bloat?  (John R Pierce <pierce@hogranch.com>)
List pgsql-general
Our app makes extensive use of temp tables, and this causes a
significant amount of bloat that can often only be cleared with a manual
vacuum process. We're looking for a better way that doesn't involve
locking, we found pg_repack and pg_reorg  and were wondering if anybody
here could weigh in on using this instead of using vacuum?

pg_repack:
https://github.com/reorg/pg_repack

pg_reorg
http://reorg.projects.pgfoundry.org/

Thanks in advance,

Ben


pgsql-general by date:

Previous
From: Torsten Förtsch
Date:
Subject: Is http://www.postgresql.org/docs/9.3/static/row-estimation-examples.html up to date?
Next
From: Tom Lane
Date:
Subject: Re: vacuum vs pg_repack for clearing bloat?