On Thu, 2010-12-30 at 10:45 -0500, Tom Lane wrote:
> Comments?
Thanks for working on this. I love the reuse of tuple flags; I can't
help feeling that opens up doors, just not sure how yet...
--
Simon Riggs http://www.2ndQuadrant.com/books/
PostgreSQL Development, 24x7 Support, Train
On Thu, Dec 30, 2010 at 11:50 PM, Robert Haas wrote:
> On Thu, Dec 30, 2010 at 10:45 AM, Tom Lane wrote:
> > I had an epiphany about this topic, or actually two of them.
> >
> > 1. Whether or not you think there's a significant performance reason
> > to support hash right joins, there's a functi
Robert Haas writes:
> On Thu, Dec 30, 2010 at 10:45 AM, Tom Lane wrote:
>> ... But we only need one bit, so what about commandeering
>> an infomask bit in the tuple itself? For the initial implementation
>> I'd be inclined to take one of the free bits in t_infomask2. We could
>> actually get aw
On Thu, Dec 30, 2010 at 10:45 AM, Tom Lane wrote:
> I had an epiphany about this topic, or actually two of them.
>
> 1. Whether or not you think there's a significant performance reason
> to support hash right joins, there's a functionality reason. The
> infrastructure for right join could just a
I had an epiphany about this topic, or actually two of them.
1. Whether or not you think there's a significant performance reason
to support hash right joins, there's a functionality reason. The
infrastructure for right join could just as easily do full joins.
And AFAICS, a hash full join would o
