Re: [HACKERS] samekeys

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
Cc: hackers(at)postgreSQL(dot)org (PostgreSQL-development)
Subject: Re: [HACKERS] samekeys
Date: 1999-02-09 00:02:22
Message-ID: 17752.918518542@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> writes:
> I think I have solved the optimizer problem. It appears in samekeys().
> Can someone check that function, and see if you come up with the same
> fix I do (without knowing my fix)?

"member" -> "equal", perhaps?

I looked at that before and thought it was a little strange, but I
didn't and still don't understand the data structures being compared.

I also wondered whether the two lists ought not be required to be
exactly the same length, rather than allowing keys2 to be longer.

> A 9-table join that used to run for minutes and fail now completes in
> seconds!

Pick some smaller joins and see whether the optimizer still finds
the same answer...

regards, tom lane

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 1999-02-09 01:34:52 Datetime input-parsing shortcoming
Previous Message Oliver Elphick 1999-02-09 00:02:11 HAVING bug in 6.4.2