However no space seems to be freed to the system.
Is there any way a bloody newbie can debug this behaviour?
In our experience, autovacuum is able to contain bloating of table data,
but not bloating of indexes.
You could see where the bloating is by running the following queries:
CREATE EX
On 03/04/2018 10:54, Kein Name wrote:
> Why would you want that? Do you have any control over the application? Any
"special" patterns used in the app?
Drive is running full :/
Sadly I have no control and knowledge whatsoever over/about the application.
I tuned the autovacuum parameters now for
> Why would you want that? Do you have any control over the application?
Any "special" patterns used in the app?
Drive is running full :/
Sadly I have no control and knowledge whatsoever over/about the application.
I tuned the autovacuum parameters now for the critical tables, to have it
run more
On 03/04/2018 10:00, Kein Name wrote:
> VACUUM <> VACUUM FULL
> Normally running VACUUM via autovacuum should help reuse free space but not
actually return it to the filesystem / OS (unless it happens to be the last blocks
in the data file(s)).
> Ppl in normal/average type of installations/work
> VACUUM <> VACUUM FULL
> Normally running VACUUM via autovacuum should help reuse free space but
not actually return it to the filesystem / OS (unless it happens to be the
last blocks in the data file(s)).
> Ppl in normal/average type of installations/workloads no longer (since
8.2) run VACUUM (or
On 03/04/2018 09:36, Kein Name wrote:
However no space seems to be freed to the system.
Is there any way a bloody newbie can debug this behaviour?
VACUUM <> VACUUM FULL
Normally running VACUUM via autovacuum should help reuse free space but not
actually return it to the filesystem / OS (unles
