Re: Disabling nested loops - worst case performance

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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


--
Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance


[Postgresql General]     [Postgresql PHP]     [PHP Users]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Yosemite]

  Powered by Linux