Alvaro,
> 1. vacuum_cost_delay does not affect vacuum full
> 2. vacuum full is always blocking, regardless of settings
So only way is to disable other database acces if vacuum full is required.
> So I gather you're not doing any vacuuming, eh?
Log files for every day are full of garbage messages below.
So I hope that vacuum is running well, isn't it ?
Andrus.
2008-11-19 00:00:48 EET 11728 1 LOG: autovacuum: processing database
"postgres"
2008-11-19 00:01:48 EET 11729 1 LOG: autovacuum: processing database
"mydb1"
2008-11-19 00:02:48 EET 11730 1 LOG: autovacuum: processing database
"emydb1"
2008-11-19 00:03:48 EET 11731 1 LOG: autovacuum: processing database
"template1"
2008-11-19 00:04:48 EET 11732 1 LOG: autovacuum: processing database
"testmydb1"
2008-11-19 00:05:48 EET 11733 1 LOG: autovacuum: processing database
"mydb3"
2008-11-19 00:06:48 EET 11734 1 LOG: autovacuum: processing database
"postgres"
2008-11-19 00:07:48 EET 11735 1 LOG: autovacuum: processing database
"mydb1"
2008-11-19 00:08:48 EET 11736 1 LOG: autovacuum: processing database
"emydb1"
2008-11-19 00:09:48 EET 11737 1 LOG: autovacuum: processing database
"template1"
2008-11-19 00:10:48 EET 11750 1 LOG: autovacuum: processing database
"testmydb1"
2008-11-19 00:11:48 EET 11751 1 LOG: autovacuum: processing database
"mydb3"
2008-11-19 00:12:48 EET 11752 1 LOG: autovacuum: processing database
"postgres"
2008-11-19 00:13:48 EET 11753 1 LOG: autovacuum: processing database
"mydb1"
2008-11-19 00:14:48 EET 11754 1 LOG: autovacuum: processing database
"emydb1"
2008-11-19 00:15:48 EET 11755 1 LOG: autovacuum: processing database
"template1"
2008-11-19 00:16:48 EET 11756 1 LOG: autovacuum: processing database
"testmydb1"
2008-11-19 00:17:48 EET 11757 1 LOG: autovacuum: processing database
"mydb3"
...
