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

Palle Girgensohn wrote:
> 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


Are not absolutelly bad but sometimes that path that you choose is not
the optimal, in postgres 7.4 use the explicit join will be less 
limitative for the planner.

Regards
Gaetano Mendola




view thread (11+ messages)  latest in thread

Message-ID: <3F78346F.5060809@bigfoot.com>
Permalink:  ../3F78346F.5060809@bigfoot.com/
Also on:    postgresql.org/message-id/3F78346F.5060809@bigfoot.com

 · 

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: mendola@bigfoot.com, girgen@pingpong.net
  Subject: Re: avoiding seqscan?
  In-Reply-To: <3F78346F.5060809@bigfoot.com>
  References: <95900000.1064782481@palle.girgensohn.se> <3F7766B3.4030705@bigfoot.com> <180710000.1064841936@durian.pingpong.net> <3F78346F.5060809@bigfoot.com>

* 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