Denis de Bernardy <ddebernardy@xxxxxxxxx> writes: > [ estimates for array && suck ] > Might this be a bug in the operator's selectivity, or am I doing something wrong? Array && uses areasel() which is only a stub :-( In the particular case here it'd be possible to get decent answers just by trying the operator against all the MCV-list entries, but it's unlikely that that would fix things for enough people to be worth the trouble. Really you'd need to maintain statistics about the element values appearing in the array column in order to get useful estimates for && queries. Jan Urbanski did something similar for tsvector columns a year or two ago, but nobody's gotten around to doing it for array columns. regards, tom lane -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
