Hi Laurens,
> Onpreface, sorry for my dummy skills on postgresql
Maybe just a silly remark of mine. Do you have indexes on your tables? If
not you will have a lot of table scans which result in high cpu load. 2
indexes which have to be present are the insrel.snumber and insrel.dnumber
to have a decent performance.
> Vacuumdb: Nope, read the manual, can I use it with the
> database running, should I use it to clean garbage and/or
> analyze the data.
The analyze part of the vacuum does something the same as costbased
optimization mode in oracle. Some other thing I discovered is that the
vacuum does not clean the largeobject table of postgresql when an image or
attachment is deleted.
Execute this and see how bad it is in your case
select loid, pageno from pg_largeobject
where loid not in (select handle from mm_attachments )
and loid not in (select handle from mm_images )
and loid not in (select handle from mm_icaches )
> Slow queries: Is there a easy way to get the slow ones (CPU
> consuming ones) Version postgresql: Requirement of app developer
> MMBase: 1.5 (also Requirement of app developer)
You could try to add the following in the config/log/log4j.xml. I can
remember that thers already was some logging in there in 1.5.
<category name="org.mmbase.module.database.MultiConnection"
class="&logger;">
<priority class="&priority;" value="info" />
</category>
Or
<category name="org.mmbase.module.database" class="&logger;">
<priority class="&priority;" value="info" />
</category>
Nico
