Re: Re: 512,600ms query becomes 7500ms... but why? Postgres 8.3 query planner quirk?

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Bryce Nesbitt <bryce2(at)obviously(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Re: 512,600ms query becomes 7500ms... but why? Postgres 8.3 query planner quirk?
Date: 2010-02-10 09:11:51
Message-ID: 162867791002100111n3cbf2164p5b9907d82174ba9@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

2010/2/10 Bryce Nesbitt <bryce2(at)obviously(dot)com>:
> Or, if you want to actually read that query plan, try:
> http://explain.depesz.com/s/qYq
>

hello,

check your work_mem sesttings. Hash join is very slow in your case.

Pavel

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

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Ing. Marcos L. Ortiz Valmaseda 2010-02-10 09:47:51 Re: [PERFORM] PostgreSQL - case studies
Previous Message Bryce Nesbitt 2010-02-10 08:29:53 Re: 512,600ms query becomes 7500ms... but why? Postgres 8.3 query planner quirk?