On Wed, Jan 15, 2014 at 05:37:27PM -0800, Lists wrote:
> it's clearing out the cruft that results from creating temp tables,
> loading a bunch of data, then dropping the table, either explicitly
> or when the connection is terminated. This causes PG disk usage to
> climb without causing any change
On 1/15/2014 5:37 PM, Lists wrote:
it's clearing out the cruft that results from creating temp tables,
loading a bunch of data, then dropping the table,
there shoudl be zero cruft. when the table is dropped, it should pooferate.
--
john r pierce 37N 122W
Lists writes:
> The process(es) creating the temp tables are not persistent, so the
> issue isn't trying to clean up bloat from a long running process, it's
> clearing out the cruft that results from creating temp tables, loading a
> bunch of data, then dropping the table, either explicitly or
On 01/15/2014 04:24 PM, Tom Lane wrote:
Lists 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_reo
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 lifespan
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 wh
Lists 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 were wondering if anybod
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
