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

Re: Any optimizations to the join code in 7.1?

From: Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu>
To: "mascarm(at)mascari(dot)com" <mascarm(at)mascari(dot)com>, "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "'pgsql-hackers(at)postgresql(dot)org'" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Any optimizations to the join code in 7.1?
Date: 2001-04-28 01:49:09
Message-ID: 3AEA2195.2415244A@alumni.caltech.edu (view raw or flat)
Thread:
Lists: pgsql-hackers
> ... 7.1 out of the box took only 2 seconds! I was amazed
> and shocked at this damned impressive improvement in planning
> speed....until I actually used the explicit JOIN syntax described in
> 11.2. Instanteous results! Instantaneous.....

But it is possible, under many circumstances, for query optimization to
be a benefit for a many-table query. The docs indicate that explicit
join syntax bypasses that, even for inner joins, so you may find that
this syntax is a net loss in performance depending on the query and your
choice of table order.

Presumably we will be interested in making these two forms of inner join
equivalent in behavior in a future release. Tom, what are the
impediments we might encounter in doing this?

                      - Thomas

In response to

Responses

pgsql-hackers by date

Next:From: balloonDate: 2001-04-28 01:53:14
Subject: after changing login password (local), CPU always 100% !!
Previous:From: Bruce MomjianDate: 2001-04-28 01:45:24
Subject: Re: Re: The new, the improved ... FTS Searching of Mailing List Archives

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