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
Lists li...@benjamindsmith.com writes:
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
On Wed, Jan 15, 2014 at 04:09:28PM -0800, Lists wrote:
Our app makes extensive use of temp tables, and this causes a
significant amount of bloat that can often only be cleared with a
Note what Tom Lane said, but why do you have bloat that can only be
cleared by vacuum? Why not drop them or
On 1/15/2014 4:09 PM, Lists wrote:
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.
whats the persistence of these temporary tables?by design, they are
meant for relatively short
On 01/15/2014 04:24 PM, Tom Lane wrote:
Lists li...@benjamindsmith.com writes:
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
