Re: Disabling nested loops - worst case performance - Mailing list pgsql-performance

From Thomas Kellerer
Subject Re: Disabling nested loops - worst case performance
Date
Msg-id ilvept$o6o$1@dough.gmane.org
Whole thread Raw
In response to Disabling nested loops - worst case performance  (Anssi Kääriäinen <anssi.kaariainen@thl.fi>)
Responses Re: Disabling nested loops - worst case performance  (Anssi Kääriäinen <anssi.kaariainen@thl.fi>)
List pgsql-performance
Anssi Kääriäinen, 18.03.2011 08:15:
> Hello list,
>
> I am working on a Entity-Attribute-Value (EAV) database using
> PostgreSQL 8.4.7. The basic problem is that when joining multiple
> times different entities the planner thinks that there is vastly less
> rows to join than there is in reality and decides to use multiple
> nested loops for the join chain.

Did you consider using hstore instead?

I think in the PostgreSQL world, this is a better alternative than EAV and most probably faster as well.

Regards
Thomas

pgsql-performance by date:

Previous
From: Vitalii Tymchyshyn
Date:
Subject: Re: Disabling nested loops - worst case performance
Next
From: Anssi Kääriäinen
Date:
Subject: Re: Disabling nested loops - worst case performance