Since the production database is running, I plan to do now is this
1. Set archive_timeout = 20m (Does the change require db restart to take
2. Set autovacuum=on and track_count=on (Does the change require db restart
to take effect?)
Does that mean we are running autovacuum?
3. Run VACUUM FREEZE ANALYZE since bulk loading was done earlier. (Can this
be done while the db is active and on production?)
All 3 steps is to lower the WAL files that are being shipped out.
Is this a workable action to achieve the result required?
In response to
pgsql-admin by date
|Next:||From: Stephen Frost||Date: 2011-04-01 02:22:09|
|Subject: Re: Too many WAL(s) despite low transaction|
|Previous:||From: Rajendra prasad||Date: 2011-04-01 02:01:40|
|Subject: Index size growing|