Re: Use merge-based matching for MCVs in eqjoinsel - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Use merge-based matching for MCVs in eqjoinsel
Date
Msg-id 843059.1763405073@sss.pgh.pa.us
Whole thread Raw
In response to Re: Use merge-based matching for MCVs in eqjoinsel  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
I wrote:
> Actually, after sleeping on it it seems like the obvious thing is
> to test "sslot1.nvalues * sslot2.nvalues", since the work we are
> thinking about saving scales as that product.  But I'm not sure
> what threshold value to use if we do that.  Maybe around 10000?

Or maybe better, since we are considering an O(m*n) algorithm
versus an O(m+n) one, we could check whether

sslot1.nvalues * sslot2.nvalues - (sslot1.nvalues + sslot2.nvalues)

exceeds some threshold.  But that doesn't offer any insight into
just what the threshold should be, either.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Sami Imseih
Date:
Subject: Re: Report oldest xmin source when autovacuum cannot remove tuples
Next
From: Nathan Bossart
Date:
Subject: Re: postgresql.conf.sample tab width