|
Pre-1.1 Confluence would add an extra copy of an index/constraint on a confluence database table every time the server was restarted. This has caused some users to run into memory problems such as CONF-1204 when the maximum limit of indexes per table has been reached. To check if this problem exists in your installation, first open up a console window to your database. For MySQL users, run:
> show index from CONTENT;
You can verify this problem exists if you notice multiple indexes referencing the same column name like the following: BLOGSPACEID is duplicated by BLOGSPACEID_2 and both reference the BLOGSPACEID column +---------+------------+---------------+--------------+-------------+ | Table | Non_unique | Key_name | Seq_in_index | Column_name | +---------+------------+---------------+--------------+-------------+ | CONTENT | 0 | PRIMARY | 1 | CONTENTID | | CONTENT | 1 | BLOGSPACEID | 1 | BLOGSPACEID | | CONTENT | 1 | PAGEID | 1 | PAGEID | | CONTENT | 1 | PARENTID | 1 | PARENTID | | CONTENT | 1 | PREVVER | 1 | PREVVER | | CONTENT | 1 | SPACEID | 1 | SPACEID | | CONTENT | 1 | DESCSPACEID | 1 | DESCSPACEID | | CONTENT | 1 | BLOGSPACEID_2 | 1 | BLOGSPACEID | | CONTENT | 1 | PAGEID_2 | 1 | PAGEID | | CONTENT | 1 | PARENTID_2 | 1 | PARENTID | | CONTENT | 1 | PREVVER_2 | 1 | PREVVER | | CONTENT | 1 | SPACEID_2 | 1 | SPACEID | | CONTENT | 1 | DESCSPACEID_2 | 1 | DESCSPACEID | +---------+------------+---------------+--------------+-------------+ For PostgreSQL users, run: > \d content; You can verify this problem exists if you get lots of RI_ConstraintTriggers being displayed like the following:
Example:
Triggers: RI_ConstraintTrigger_214459,
RI_ConstraintTrigger_214460,
RI_ConstraintTrigger_214465,
RI_ConstraintTrigger_214466,
RI_ConstraintTrigger_214468,
RI_ConstraintTrigger_214469,
RI_ConstraintTrigger_214482,
RI_ConstraintTrigger_214483,
RI_ConstraintTrigger_214484,
If you observe this in your database, you can fix the problem by performing the following:
|
Add Comment