Re: Simply join in PostrgeSQL takes too long

From: Manfred Koizar <mkoi-pg(at)aon(dot)at>
To: Rod Taylor <pg(at)rbt(dot)ca>
Cc: Vitaly Belman <vitalib(at)012(dot)net(dot)il>, Postgresql Performance <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Simply join in PostrgeSQL takes too long
Date: 2004-04-29 17:13:49
Message-ID: lkd29018sbqg8bhcr3dabfjf6u6jckib3t@email.aon.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Wed, 28 Apr 2004 08:23:35 -0400, Rod Taylor <pg(at)rbt(dot)ca> wrote:
>The below plpgsql forces the kind of algorithm we wish the planner could
>choose. It should be fairly quick irregardless of dataset.

That reminds me of hash aggregation. So here's another idea for Vitaly:

SELECT book_id
FROM ...
WHERE ...
GROUP BY book_id
LIMIT ...

Servus
Manfred

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Josh Berkus 2004-04-29 17:23:58 Re: Use arrays or not?
Previous Message Manfred Koizar 2004-04-29 17:03:03 Re: planner/optimizer question