Re: Design notes for EquivalenceClasses

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Gavin Sherry <swm(at)linuxworld(dot)com(dot)au>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Design notes for EquivalenceClasses
Date: 2007-01-18 00:46:04
Message-ID: 15246.1169081164@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Gavin Sherry <swm(at)linuxworld(dot)com(dot)au> writes:
> I was thinking about this, but in relation to hash joins. A hash join
> cannot be guaranteed to produce output sorted according to the pathkey of
> the outer relation (as explained in the existing README). I wonder,
> however, if it might be useful for hash join to pass a hint that the
> output is known ordered (i.e., the join was not split into multiple
> batches).

Yeah, I've considered that, but I think it'd have to be the other way
around: the planner tells the executor that it's assuming the output is
sorted, hence do not split into multiple batches. This has the usual
assortment of problems if the planner has badly misestimated the
rowcount :-(

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2007-01-18 00:50:31 Re: Function execution costs 'n all that
Previous Message Jeff Davis 2007-01-18 00:37:53 Re: Function execution costs 'n all that