On 10/15/19 5:54 AM, Strahil wrote:
Can someonw clarify whether the DB will grow forever , if we never do a vacuum
(either with these commands or via the engine-upgrade)?
The postgres database runs autovacuum regularly by default and engine
defines some vacuum variables in postgresql.conf t
Can someonw clarify whether the DB will grow forever , if we never do a vacuum
(either with these commands or via the engine-upgrade)?
Best Regards,
Strahil NikolovOn Oct 14, 2019 17:03, Lucie Leistnerova
wrote:
>
>
> On 10/14/19 3:36 PM, Chris Adams wrote:
> > Once upon a time, Lucie Leistne
On 10/14/19 3:36 PM, Chris Adams wrote:
Once upon a time, Lucie Leistnerova said:
Ah, you are right. dwh-vacuum was added in 4.2.
Just for interest, I tried this on my 4.3.6 dev setup, and it just
gives:
[root@engine ~]# dwh-vacuum
/usr/bin/dwh-vacuum: line 47: vacuumdb: command not found
L
Once upon a time, Lucie Leistnerova said:
> Ah, you are right. dwh-vacuum was added in 4.2.
Just for interest, I tried this on my 4.3.6 dev setup, and it just
gives:
[root@engine ~]# dwh-vacuum
/usr/bin/dwh-vacuum: line 47: vacuumdb: command not found
Looks like it needs the SCL enablement tha
On 10/14/19 3:07 PM, Chris Adams wrote:
Once upon a time, Lucie Leistnerova said:
you can use engine tools: engine-vacuum and dwh-vacuum.
It can do full vacuum with -f option and also it runs with
engine-setup when you choose it.
engine-vacuum doesn't appear to touch the DWB DB, and I don't h
Once upon a time, Lucie Leistnerova said:
> you can use engine tools: engine-vacuum and dwh-vacuum.
> It can do full vacuum with -f option and also it runs with
> engine-setup when you choose it.
engine-vacuum doesn't appear to touch the DWB DB, and I don't have a
dwh-vacuum (on 4.1). After read
Hi Pavel,
you can use engine tools: engine-vacuum and dwh-vacuum.
It can do full vacuum with -f option and also it runs with engine-setup
when you choose it.
On 10/11/19 4:36 PM, Pavel Šipoš wrote:
Hi!
We have similar problem and it looks like psql vacuuming isn't working
properly.
I expect
Hi!
We have similar problem and it looks like psql vacuuming isn't working
properly.
I expect that this problem will be gone when we will upgrade ovirt to
latest version.
Until then we are performing weekly vacuuming of top N (usualy 4) tables
by "external size" in ovirt_engine_history databas
On October 11, 2019 3:43:55 PM GMT+03:00, Chris Adams wrote:
>On my oVirt 4.1.9 cluster, the hosted engine filled up its disk last
>night (it was deployed from the engine appliance image and had a 20G
>root and 5G swap). I gained a little space by trimming down swap, but
>I
>need to clean it up.
9 matches
Mail list logo
