c2c-oerpscenario team mailing list archive

[xrg <xrg@xxxxxxxxx>]

On Tuesday 02 November 2010, you wrote:
> No, it doesn't drop it. It drops (lang, type, name, src) and adds a hash
> on (src) only.

@albert: don't worry, we're not going to bring back any btree index on
src.

@ferdinard: we are going to port some changes from the pg84 branch into trunk, 
so that the number of ir_translation queries is drastically reduced. However, 
adding res_id as a last column to the index still seems fair.

When thinking about indexes, we also have to consider their size in the 
database. That is, if we add too many indexes, we are filling our disks (and 
running memory) with data, that may in turn decrease overall performance.

-- 
[6.0RC1] performance 
https://bugs.launchpad.net/bugs/669919
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.

Status in OpenObject Server: New

Bug description:
this 2 indices should improve performance if a lot of translations are to be processed.

    "ir_translation_ltnr" btree (name, lang, type, res_id)
    "ir_translation_ltns" btree (name, lang, type, src)


currently defined only:
 "ir_translation_ltn" btree (name, lang, type)