From: Thomas Kellerer <spam_eater@gmx.net>
To: pgsql-performance@postgresql.org
Subject: Re: Disabling nested loops - worst case performance
Date: Fri, 18 Mar 2011 12:14:05 +0100
Message-ID: <ilvept$o6o$1@dough.gmane.org> (raw)
In-Reply-To: <4D8306A7.7020205@thl.fi>
References: <4D8306A7.7020205@thl.fi>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: spam_eater@gmx.net
Subject: Re: Disabling nested loops - worst case performance
In-Reply-To: <ilvept$o6o$1@dough.gmane.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox