Opush 3.2.1 release

The OBM Core Team is releasing today a new version of Opush, the OBM ActiveSync server.

There is a small changelog for this release, but your synchronization can perform much better with it! So we strongly advise you to upgrade to this version.


The job title is not on the contact display name anymore


Faster synchronization of devices

See the JIRA issue navigator if you want to see the list and more details.

How to create OP-247 indexes manually ?

Indexes on the table "opush_sync_state" can be missing on some OBM installations. As many of our customers have already created them manually, eventually with custom names, it is almost impossible for us to manage such indexes creation automatically. It is why we suggest you to create them if you need.

1) Connect to your postgresql server

$ su postgres -c "psql obm"

2) Check your table indexes

obm=# \d opush_sync_state
                                       Table "public.opush_sync_state"
    Column     |            Type             |                           Modifiers                           
 id            | integer                     | not null default nextval('opush_sync_state_id_seq'::regclass)
 sync_key      | character varying(64)       | not null
 collection_id | integer                     | not null
 device_id     | integer                     | not null
 last_sync     | timestamp without time zone | not null
    "opush_sync_state_pkey" PRIMARY KEY, btree (id)
    "opush_sync_state_sync_key_key" UNIQUE CONSTRAINT, btree (sync_key)
Foreign-key constraints:
    "opush_sync_state_device_id_fkey" FOREIGN KEY (device_id) REFERENCES opush_device(id) ON DELETE CASCADE

3) If you don't have any index for "last_sync", "collection_id" or "device_id", like in the exemple above, create them:

obm=# CREATE INDEX ON opush_sync_state (last_sync);
obm=# CREATE INDEX ON opush_sync_state (collection_id);
obm=# CREATE INDEX ON opush_sync_state (device_id);


How to get it ?

To upgrade from a previous version of Opush follow this section.