2006/10/1, Matthew T. O'Connor <matthew@zeut.net>:
MaXX wrote:
>> There are 10-15 postmaster processes running which use all the CPU
>> power.
>> A restart of tomcat and then postgresql results in the same situation.
>> Some postgres processes are in DELETE waiting or SELECT waiting.
>> VACUUM runs through in just about 1-2 seconds and is run via cron
>> every minute and reports that the fsm setting are high enough.
>
> Pure speculation: are you sure you aren't vacuuming too agressively?
Have you tried autovacuum? You can manually tweak the settings so that
your hot spot tables are vacuumed aggressivly. One of the main upsides
to autovacuum is tha tit saves cycles, that is, it only vacuums when you
need it.
---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend
Autovacuum is enabled and runs in addition to the configured cronjob
vacuums. I will attach logfiles to the reply to Toms mail, so please
have a look at it if autovacuum can be reconfigured to replace the
cronjobs.
thx,
Peter
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
