On 07/19/2017 06:37 PM, Tom Lane wrote:
> Dmitry Lazurkin writes:
>> I am trying to find workaround for cross-column statistics.
>> ...
>> Worn estimate. Planner doesn't use statistics. In code I see usage of
>> function scalargtsel which returns default selectivity because
>> ROW('tag1', 0.9)::ta
Hello.
I am trying to find workaround for cross-column statistics. For example, I
have tags with similarity:
select version();
version
-
Stephen Frost writes:
> * Tom Lane (t...@sss.pgh.pa.us) wrote:
>> Yeah, that's because eval_const_expressions doesn't know how to fold
>> a constant RowExpr to a simple Const. I have a patch laying about
>> someplace to improve that, but I keep forgetting about it until
>> we're in beta phase :-(
Tom,
* Tom Lane (t...@sss.pgh.pa.us) wrote:
> Dmitry Lazurkin writes:
> > I am trying to find workaround for cross-column statistics.
> > ...
> > Worn estimate. Planner doesn't use statistics. In code I see usage of
> > function scalargtsel which returns default selectivity because
> > ROW('tag1'
Dmitry Lazurkin writes:
> I am trying to find workaround for cross-column statistics.
> ...
> Worn estimate. Planner doesn't use statistics. In code I see usage of
> function scalargtsel which returns default selectivity because
> ROW('tag1', 0.9)::tag_sim is not Const.
Yeah, that's because eval_
Hello.
I am trying to find workaround for cross-column statistics. For example,
I have tags with similarity:
select version();
version
-
