Andrey Zhidenkov wrote
> I'm confused about this:
>
> [postgres@srv log]$ grep autovacuum ~/data/postgresql.conf
> autovacuum = off # Enable autovacuum subprocess? 'on'
> log_autovacuum_min_duration = 0 # -1 disables, 0 logs all actions and
> autovacuum_naptime = 10min # time between autovacuum runs
>
> So, as you can see, autovacuum is disabled now and I could not seen any
> autovacuum tasks about few hours. But now
> I can see this:
>
> srv=# select backend_start, query from pg_stat_activity where query ilike
> '%vacuum%';
> backend_start |
> query
>
> -------------------------------+---------------------------------------------------------------------------------
> 2014-07-29 21:38:42.882383+04 | select backend_start, query from
> pg_stat_activity where query ilike '%vacuum%';
> 2014-07-30 10:21:51.5511+04 | autovacuum: VACUUM ANALYZE customer_email
> 2014-07-30 10:43:19.49936+04 | autovacuum: VACUUM ANALYZE cdr_tech
> (3 rows)
>
> The problem is that table cdr_tech is very large (70Gb) and I couldn't
> wait
> while autovacuum is finished, I would like to run vacuum manually at night
> time.
>
> Whan I do wrong?
>
> Best regards, Andrey Zhidenkov
>
> _
> ASCII ribbon campaign ( )
> against HTML e-mail X
> / \
The obvious question is whether you sighup/rebooted the server after making
the change?
It helps to show what your session sees as the current guc value.
David J.
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/Can-postgres-run-autovacuum-tasks-when-autovacuum-is-disabled-tp5813253p5813254.html
Sent from the PostgreSQL - admin mailing list archive at Nabble.com.