hi tom ...
the idea behind this is to disable the stats on a certain column
entirely.
this would give me more control about the plan. in this special case
data is changing so frequently that the default values are ways
better than trying to keep the "real" stats up to date.
in case of defau
Hans-Juergen Schoenig <[EMAIL PROTECTED]> writes:
> i came across some interesting behavior of pg_stats and i am not sure
> if this is something we should treat the way we do it.
Setting target zero means "expend no work on this column". In my book
that includes not doing anything to any pre-exis
i came across some interesting behavior of pg_stats and i am not sure
if this is something we should treat the way we do it.
consider:
test_hans=# select * from pg_stats where attname = 'id' and tablename
= 't_testhugo';
schemaname | tablename | attname | null_frac | avg_width |
n_distinct
