pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jim C. Nasby <jim@nasby.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Josh Berkus <josh@agliodbs.com>
Cc: pgsql-performance <pgsql-performance@postgresql.org>
Cc: pgsql-hackers@postgresql.org
Subject: Re: [PERFORM] Hypothetical suggestions for planner, indexing improvement
Date: Wed, 7 May 2003 00:08:01 -0500
Message-ID: <20030507000801.E66185@flake.decibel.org> (raw)
In-Reply-To: <24779.1052228707@sss.pgh.pa.us>
References: <200305051219.58955.josh@agliodbs.com>
	<22292.1052195133@sss.pgh.pa.us>
	<200305052133.33680.josh@agliodbs.com>
	<20030506080747.C66185@flake.decibel.org>
	<24779.1052228707@sss.pgh.pa.us>

On Tue, May 06, 2003 at 09:45:07AM -0400, Tom Lane wrote:
> "Jim C. Nasby" <jim@nasby.net> writes:
> > It would be nice to add support for multi-column IN..
> > WHERE (a, b, c) IN (SELECT a, b, c ...)
> 
> RTFM...

As someone pointed out, the documentation says you can't. In this case
the docs are wrong (I've added a note).

> > BTW, does postgresql handle IN and EXISTS differently?
> 
> Yes.
> 
> > Theoretically if the optimizer was good enough you could transform one
> > to the other and not worry about it.
> 
> No.  They have different responses to NULLs in the subselect result.

They appear to operate the same... what's different?
-- 
Jim C. Nasby (aka Decibel!)                    jim@nasby.net
Member: Triangle Fraternity, Sports Car Club of America
Give your computer some brain candy! www.distributed.net Team #1828

Windows: "Where do you want to go today?"
Linux: "Where do you want to go tomorrow?"
FreeBSD: "Are you guys coming, or what?"




view thread (16+ messages)  latest in thread

Message-ID: <20030507000801.E66185@flake.decibel.org>
Permalink:  ../20030507000801.E66185@flake.decibel.org/
Also on:    postgresql.org/message-id/20030507000801.E66185@flake.decibel.org

 · 

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: jim@nasby.net, tgl@sss.pgh.pa.us, josh@agliodbs.com, pgsql-hackers@postgresql.org
  Subject: Re: [PERFORM] Hypothetical suggestions for planner, indexing improvement
  In-Reply-To: <20030507000801.E66185@flake.decibel.org>
  References: <200305051219.58955.josh@agliodbs.com> <22292.1052195133@sss.pgh.pa.us> <200305052133.33680.josh@agliodbs.com> <20030506080747.C66185@flake.decibel.org> <24779.1052228707@sss.pgh.pa.us> <20030507000801.E66185@flake.decibel.org>

* 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