pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Daniel Lopez <ridruejo@atm9.com.dtu.dk>
To: maillist@candle.pha.pa.us
Cc: rison@biochemistry.ucl.ac.uk
Cc: tgl@sss.pgh.pa.us
Cc: pgsql-sql@hub.org
Subject: Re: [SQL] Subselect performance
Date: Tue, 21 Sep 1999 22:54:40 +0000 ()
Message-ID: <199909212254.AAA13731@atm9.com.dtu.dk> (raw)
In-Reply-To: <199909211918.PAA14232@candle.pha.pa.us>


> It is not your fault.  We frequently get reports of this type, and the
> behavior of the subquery is very non-intuitive.  You would think that a
> subquery and a join would have the same performance, but because of the
> limitation of subqueries as being nested loop joined, this is not the
> case, and subqueries are slower.  We tell people to rewrite their query
> as EXISTS, but by the time we tell them that, they have already spent
> much time trying to figure out why the query is so slow, and I am sure
> many people don't even know about the EXISTS workaround.

You are right: I spend some time scratching my head, then some time
searching the mailing lists and I finally made the query with a EXISTS,
which works great for  me :) Thanks
Can this be a candidate to include in the FAQ? 

On the same idea, is there any good document out there with all the SQL
"recipes" or common practice for things like : "Give me all the rows which
have this value in this column more than once, etc"
I do it with: 
select my_index, count(my_index) from my_table  group by my_index having
count(my_index) > 1;

But this is a common query and would be interested in knowing which is the
commonly accepted way of doing this

Regards

Daniel



view thread (8+ messages)  latest in thread

Message-ID: <199909212254.AAA13731@atm9.com.dtu.dk>
Permalink:  ../199909212254.AAA13731@atm9.com.dtu.dk/
Also on:    postgresql.org/message-id/199909212254.AAA13731@atm9.com.dtu.dk

 · 

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-sql@postgresql.org
  Cc: ridruejo@atm9.com.dtu.dk, maillist@candle.pha.pa.us, rison@biochemistry.ucl.ac.uk, tgl@sss.pgh.pa.us, pgsql-sql@hub.org
  Subject: Re: [SQL] Subselect performance
  In-Reply-To: <199909212254.AAA13731@atm9.com.dtu.dk>
  References: <199909211918.PAA14232@candle.pha.pa.us> <199909212254.AAA13731@atm9.com.dtu.dk>

* 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