list!)
--
Bastian Voigt
Neumünstersche Straße 4
20251 Hamburg
telefon +49 - 40 - 67957171
mobil +49 - 179 - 4826359
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
saturated and the vacuum just pushes it over the edge. In which case
you'll either need more/better disks or to find a quiet time once a
day to vacuum and just do so then.
Yes, that was definitely the case. But now everything runs smoothly
again, so I don't think I need to buy new dis
rward to a laid-back weekend..
Richard, Kristo, Alvaro, thanks 1000 times for responding so quickly
:-)
--
Bastian Voigt
Neumünstersche Straße 4
20251 Hamburg
telefon +49 - 40 - 67957171
mobil +49 - 179 - 4826359
---(end of broadcast)---
TIP 2: D
y waiting transactions, killing vacuum
process $vacuumpid..."
kill $vacuumpid
fi
echo "Sleeping 30 Seconds"
sleep 30
done
--
Bastian Voigt
Neumünstersche Straße 4
20251 Hamburg
telefon +49 - 40 - 67957171
mobil +49 - 179 - 4826359
tive, it might be simpler just to
run your own vacuum-ing from a cron job.
Well, it is one of the most active, but there are others. pg_autovacuum
seems to do a very good job, apart from this one table...
--
Bastian Voigt
Neumünstersche Straße 4
20251 Hamburg
telefon +49 - 40 - 67957171
mo
(cache_id)
Thanks in advance for any hints!
--
Bastian Voigt
Neumünstersche Straße 4
20251 Hamburg
telefon +49 - 40 - 67957171
mobil +49 - 179 - 4826359
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your
