Re: Functions returning sets

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Don Baccus <dhogaza(at)pacifier(dot)com>
Cc: Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com>, Hackers List <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Functions returning sets
Date: 2001-05-20 00:44:09
Message-ID: 7636.990319449@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Don Baccus <dhogaza(at)pacifier(dot)com> writes:
> What's so hard about writing "IN" rather than "=" ???

Even more to the point, if we did adopt such a (crazy IMHO)
interpretation of '=', what makes anyone think that it'd be
any more efficient than IN?

AFAICT, mlw is hoping that redefining '=' would magically avoid the
performance problems with IN, but my bet is it'd be just the same.

What we need to do is teach the system how to handle WHERE ... IN ...
as a form of join. Changing semantics of operators isn't necessary
nor helpful.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2001-05-20 00:45:20 Re: Functions returning sets
Previous Message Bruce Momjian 2001-05-20 00:38:25 Re: Fix for tablename in targetlist