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

Re: Simply join in PostrgeSQL takes too long

From: Rod Taylor <pg(at)rbt(dot)ca>
To: Manfred Koizar <mkoi-pg(at)aon(dot)at>
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:36:47
Message-ID: 1083260206.30065.300.camel@jester (view raw or flat)
Thread:
Lists: pgsql-performance
On Thu, 2004-04-29 at 13:13, Manfred Koizar wrote:
> 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:

The reason for the function is that the sort routines (hash aggregation
included) will not stop in mid-sort, although I believe that feature is
on the TODO list.

I believe Vitaly will achieve 10ms or less query times using that
function.



In response to

Responses

pgsql-performance by date

Next:From: Manfred KoizarDate: 2004-04-29 17:59:13
Subject: Re: Simply join in PostrgeSQL takes too long
Previous:From: Josh BerkusDate: 2004-04-29 17:23:58
Subject: Re: Use arrays or not?

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