From: Rod Taylor <pg@rbt.ca>
To: Manfred Koizar <mkoi-pg@aon.at>
Cc: Vitaly Belman <vitalib@012.net.il>
Cc: Postgresql Performance <pgsql-performance@postgresql.org>
Subject: Re: Simply join in PostrgeSQL takes too long
Date: Thu, 29 Apr 2004 13:36:47 -0400
Message-ID: <1083260206.30065.300.camel@jester> (raw)
In-Reply-To: <lkd29018sbqg8bhcr3dabfjf6u6jckib3t@email.aon.at>
References: <282909734.20040428002740@012.net.il>
<1083103293.30065.100.camel@jester>
<tlpu80tqhmnpc2sl63boejki6o4vbn1p3q@email.aon.at>
<1083155014.30065.189.camel@jester>
<lkd29018sbqg8bhcr3dabfjf6u6jckib3t@email.aon.at>
On Thu, 2004-04-29 at 13:13, Manfred Koizar wrote:
> On Wed, 28 Apr 2004 08:23:35 -0400, Rod Taylor <pg@rbt.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.
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: pg@rbt.ca, mkoi-pg@aon.at, vitalib@012.net.il
Subject: Re: Simply join in PostrgeSQL takes too long
In-Reply-To: <1083260206.30065.300.camel@jester>
* 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