Skip site navigation (1) Skip section navigation (2)

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 (view raw or flat)
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

pgsql-performance by date

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

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group