Community: Framework mailing list archives

expert-framework@mail.odoo.com

Re: unused database indexes

by
Graeme Gellatly
- 07/29/2016 16:56:56

Used in production for 4 years. The cost is by far worth the benefit IMO. Multiple orders of magnitude faster searches on things like partner names, sale names, products, account moves. No noticeable write slow down. Use gin for master data, gist for stuff that changes regularly, although haven't tried gin on regularly changing data since they improved it's write speed.

The main issue for others will be lack of unaccent support as postgres treats unaccent as volatile by default. Idk what a standard Odoo index / data split looks like but ours is roughly 50 50.


On Thu, 28 Jul 2016 7:13 PM Alexandre Fayolle <alexandre.fayolle@camptocamp.com> wrote:
On 27/07/2016 17:01, Leonardo Rochael Almeida wrote:

> Another point raised in the original thread was the fact that most CHAR
> field indexes are useless since most searches on these fields are
> through LIKE and ILIKE operators.
> 
> For these cases, we could be using trigram indexes:
> 
> https://www.postgresql.org/docs/current/static/pgtrgm.html
> 

Careful evaluation of trigram indexes should be done. I'm concerned of
the cost of these, both disk-wise and CPU-wise for the often updated
tables.

-- 
Alexandre Fayolle
Chef de Projet
Tel : +33 4 58 48 20 30

Camptocamp France SAS
Savoie Technolac, BP 352
73377 Le Bourget du Lac Cedex
http://www.camptocamp.com

_______________________________________________
Mailing-List: https://www.odoo.com/groups/community-framework-62
Post to: mailto:expert-framework@mail.odoo.com
Unsubscribe: https://www.odoo.com/groups?unsubscribe