- #22154: Change : in aggregator block IDs to -, the colon is an illegal character and causes problems in CSS.

- Patch #19768 by danielc: line 593 in version 1.109 of database.pgsql is problematic. The line creates a unique index for sid. But, sid is already a primary key so doesn't need a unique index on it. Let alone, the syntax is wrong due to wrapping the table name in {}'s. This patch removes the line.

- Updated the start date of the updates.

  terms are matched, the query would become very slow.

- Bug #18597: updated the database scheme.  Renamed poll.voters to poll.polled.

- Patch #12497 by Morbus: Just working on a profile reporting idea and spotted that the following fields appear to have incorrect type definitions:
profile_values.fid = int(11)
profile_values.uid = int(11)

These both appear inconsistant with the rest of the database (that I have seen i.e. user tables) where they are defined as int(10). The profile_fields.fid is defined as int(10) also.

- Modified patch #18328 by Neil: currently the two forum topic blocks share a number of topics in block setting. This is a bit confusing since configuring one blockshould not affect another block.  Fixed some indentation as well.

   1. Removed a duplicate line from the changes to update.inc.
   2. Excluded the session.inc changes: they did not make sense to me.
   3. Excluded the search related changes in the node and search module. According to Steven these are not correct.

- The update for the twin comments was 'borken' and had several bugs.

- Patch #17747 by Adrian: first round of PostgreSQL updates!

- Patch #10425 by ccourtne and walkah: added admin screens to maintain forums instead of forcing the user to add a taxonomy.

- Patch #16074 by Andre Molnar: add configuration option to show blocks only on pages of certain node type.

  Modified the patch to remove some redundant code, to translate strings, and to better use the menu system.

- Patch #15962 by Goba: no need to drop the accesslog table to add a new primary key.

- Patch #6847 by Gerhard: replaced vocabulary->nodes by a separate table and tidied up the taxonomy API a bit.  This fixes a number of issues.

  We added a 'severity' column to watchdog():
    watchdog($type, $message, $link) --> watchdog($type, $message, $severity, $link);

    * Specify a severity in case you are reporting a warning or error.
    * The $link-parameter is now the fourth parameter instead of the third.

  TODO: document this in the upgrade guide.