pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Palle Girgensohn <girgen@pingpong.net>
To: pgsql-performance@postgresql.org
Subject: Re: avoiding seqscan?
Date: Mon, 29 Sep 2003 15:45:02 +0200
Message-ID: <202370000.1064843102@durian.pingpong.net> (raw)

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

> 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

Ah, OK. True! In this case though, the sql questions are crafted with great 
care, since we have a lot of data in a few of the tables, other are almost 
empty, so we try to limit the amount of data as early as possible. Our 
experience says that we often do a better job than the planner, since we 
know which tables are "fat". Hence, we have actually moved to exlicit joins 
in questions and sometimes gained speed.

But, in the general case, implicit might be better, I guess.

Regards,
Palle






view thread (11+ messages)  latest in thread

Message-ID: <202370000.1064843102@durian.pingpong.net>
Permalink:  ../202370000.1064843102@durian.pingpong.net/
Also on:    postgresql.org/message-id/202370000.1064843102@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
  Subject: Re: avoiding seqscan?
  In-Reply-To: <202370000.1064843102@durian.pingpong.net>
  References: <202370000.1064843102@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