Re: Selecting across Multiple Tables

From: Doug McNaught <doug(at)wireboard(dot)com>
To: Tielman J de Villiers <tjdevil(at)bondnet(dot)co(dot)za>
Cc: "'Antonio Fiol =?iso-8859-1?q?Bonn=EDn'?=" <fiol(at)w3ping(dot)com>, "'pgsql-general(at)postgresql(dot)org'" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Selecting across Multiple Tables
Date: 2001-12-05 17:43:37
Message-ID: m3k7w1h8ae.fsf@belphigor.mcnaught.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Tielman J de Villiers <tjdevil(at)bondnet(dot)co(dot)za> writes:

> The main issue however is why postgres 7.1 works fine (and quick) on "WHERE"
> statements such as
>
> >Where 1.id = (select last_value from sequence) and
> > 2.id = (select last_value from sequence) and
> > 3.id = (select last_value from sequence) and
> > 4.id = (select last_value from sequence) and
>
> While postgres 6.2 drops dead on it, and works slow on "WHERE" such as
> >Where 1.id = (select last_value from sequence) and
> > 2.id = 1.id and
> > 3.id = 1.id and
> > 4.id = 1.id and
> > 5.id = 1.id and

I would say the answer is that 7.1 has at least 2 years' worth of
improvement and optimization over 6.5.2. There is no reason to be
running 6.X in this day and age, and a lot of reasons not to be.

-Doug
--
Let us cross over the river, and rest under the shade of the trees.
--T. J. Jackson, 1863

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Kirk Strauser 2001-12-05 18:11:58 Re: I wrote a program to migrate Interbase -> PostgreSQL
Previous Message Patrick Henry 2001-12-05 17:41:13 PostgreSQL Callback Mechanism