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 <lleistne@redhat.com> wrote:
On 10/14/19 3:36 PM, Chris Adams wrote:
Once upon a time, Lucie Leistnerova <lleistne@redhat.com> 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 that engine-vacuum has.
My mistake, I thought it was fixed already but it was only for engine-vacuum. I've created new BZ https://bugzilla.redhat.com/show_bug.cgi?id=1761494
Thanks for catching this!
-- Lucie Leistnerova Senior Quality Engineer, QE Cloud, RHVM Red Hat EMEA
IRC: lleistne @ #rhev-qe _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/5WGD552G3GKGSI...
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 to be more efficient. Autovacuum runs standard vacuum (not FULL) and this can reclaim less space. When you have smaller environment the grow of dwh database is not to significant but with big setup it can be different. So is good to run full vacuum in some time to reclaim more space. The thing is that this takes a lot of time and tables are locked, so engine/dwh can't work with them properly and need to be stopped.
Best Regards, Strahil NikolovOn Oct 14, 2019 17:03, Lucie Leistnerova <lleistne@redhat.com> wrote:
On 10/14/19 3:36 PM, Chris Adams wrote:
Once upon a time, Lucie Leistnerova <lleistne@redhat.com> 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 that engine-vacuum has. My mistake, I thought it was fixed already but it was only for engine-vacuum. I've created new BZ https://bugzilla.redhat.com/show_bug.cgi?id=1761494
Thanks for catching this!
-- Lucie Leistnerova Senior Quality Engineer, QE Cloud, RHVM Red Hat EMEA
IRC: lleistne @ #rhev-qe _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/5WGD552G3GKGSI...
-- Lucie Leistnerova Senior Quality Engineer, QE Cloud, RHVM Red Hat EMEA IRC: lleistne @ #rhev-qe
participants (2)
-
Lucie Leistnerova -
Strahil