pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Palle Girgensohn <girgen@pingpong.net>
To: Gaetano Mendola <mendola@bigfoot.com>
To: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: avoiding seqscan?
Date: Mon, 29 Sep 2003 15:25:36 +0200
Message-ID: <180710000.1064841936@durian.pingpong.net> (raw)
In-Reply-To: <3F7766B3.4030705@bigfoot.com>
References: <95900000.1064782481@palle.girgensohn.se>
	<3F7766B3.4030705@bigfoot.com>

Will that make a difference? From what I've seen, it does not make much 
difference, but I have seen queries speed up when rewritten explicit joins. 
I guess it depends on other things, but is it really so that the explicit 
joins are bad somehow? Do you have any pointers to documentation about it, 
if so?

Thanks,
Palle

--On måndag, september 29, 2003 00.54.43 +0200 Gaetano Mendola 
<mendola@bigfoot.com> wrote:

> Palle Girgensohn wrote:
>> uu=# explain analyze
>> uu-#  select lower(substr(p.last_name,1,1)) as letter, count(*)
>> uu-#  FROM course c join group_data gd on (c.active_group_id =
>> gd.this_group_id)
>> uu-#       join person p on (gd.item_text = p.userid)
>> uu-#       join dyn_field_person dfp on (dfp.extern_item_id = 10 and
>> dfp.giver=c.giver)
>> uu-#       join dyn_field_content_person dfcp on (dfp.id =
>> dfcp.dyn_field_id and dfcp.userid=p.userid)
>> uu-#       left outer join participant pt on (pt.userid = p.userid and
>> pt.course_id = 707)
>> uu-#  WHERE c.id = 707
>> uu-#  group by 1
>> uu-# ;
>
> Why are you using this form of join ? When and if is not necessary use
> the implicit form.
>
>
> Regards
> Gaetano Mendola
>
>
>







view thread (11+ messages)  latest in thread

Message-ID: <180710000.1064841936@durian.pingpong.net>
Permalink:  ../180710000.1064841936@durian.pingpong.net/
Also on:    postgresql.org/message-id/180710000.1064841936@durian.pingpong.net

 · 

reply

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: girgen@pingpong.net, mendola@bigfoot.com
  Subject: Re: avoiding seqscan?
  In-Reply-To: <180710000.1064841936@durian.pingpong.net>
  References: <95900000.1064782481@palle.girgensohn.se> <3F7766B3.4030705@bigfoot.com> <180710000.1064841936@durian.pingpong.net>

* 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