Re: Disabling nested loops - worst case performance

From: Thomas Kellerer <spam_eater(at)gmx(dot)net>
To: pgsql-performance(at)postgresql(dot)org
Subject: Re: Disabling nested loops - worst case performance
Date: 2011-03-18 11:14:05
Message-ID: ilvept$o6o$1@dough.gmane.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Anssi Kääriäinen 2011-03-18 11:59:29 Re: Disabling nested loops - worst case performance
Previous Message Anssi Kääriäinen 2011-03-18 10:58:48 Re: Disabling nested loops - worst case performance