pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Steinar H. Gunderson <sgunderson@bigfoot.com>
To: pgsql-performance@postgresql.org
Subject: Re: [HACKERS] temporary indexes
Date: Tue, 28 Feb 2006 19:08:37 +0100
Message-ID: <20060228180837.GA1593@uio.no> (raw)
In-Reply-To: <44043A34.EE98.0025.0@wicourts.gov>
References: <44041B68.EE98.0025.0@wicourts.gov>
	<20060228164515.GS82012@pervasive.com>
	<20060228164515.GS82012@pervasive.com>
	<16076.1141146348@sss.pgh.pa.us>
	<440435BC.EE98.0025.0@wicourts.gov>
	<44043A34.EE98.0025.0@wicourts.gov>

On Tue, Feb 28, 2006 at 11:55:32AM -0600, Kevin Grittner wrote:
>> Also, EXISTS works in situations where
>> you need to compare on multiple columns, so it is useful in many
>> situations where EXISTS or MIN/MAX techniques just don't work.
> Sorry.  That should have read:
> 
> EXISTS works in situations where
> you need to compare on multiple columns, so it is useful in many
> situations where IN or MIN/MAX techniques just don't work.

Can't you just do WHERE (foo,bar) IN ( SELECT baz,quux FROM table )? I'm
quite sure I've done that a number of times.

/* Steinar */
-- 
Homepage: http://www.sesse.net/



view thread (13+ messages)  latest in thread

Message-ID: <20060228180837.GA1593@uio.no>
Permalink:  ../20060228180837.GA1593@uio.no/
Also on:    postgresql.org/message-id/20060228180837.GA1593@uio.no

 · 

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 using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: sgunderson@bigfoot.com
  Subject: Re: [HACKERS] temporary indexes
  In-Reply-To: <20060228180837.GA1593@uio.no>

* 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