Re: pgsql/src/test/regress/expected (union.out)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alfred Perlstein <bright(at)wintelcom(dot)net>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql/src/test/regress/expected (union.out)
Date: 2000-10-05 21:32:22
Message-ID: 17172.970781542@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Alfred Perlstein <bright(at)wintelcom(dot)net> writes:
>> Reimplementation of UNION/INTERSECT/EXCEPT.

> Does this mean that in the next release EXCEPT will be a lot faster?
> Will I probably be able to drop my "NOT EXISTS" hacks that I've
> been using?

UNION/INTERSECT/EXCEPT are now all basically a sort phase and a
unique-filter phase, with minor variations on what the unique filter
thinks it should output. So the cost should be O((M+N) log (M+N)) for
M+N input tuples, as opposed to O(M*N) for the old INTERSECT and
EXCEPT code.

I didn't do anything to change EXISTS ...

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Alfred Perlstein 2000-10-05 21:34:44 Re: pgsql/src/test/regress/expected (union.out)
Previous Message Alfred Perlstein 2000-10-05 21:09:38 Re: pgsql/src/test/regress/expected (union.out)