Re: Problem with n_distinct being consistently inaccurate. - Mailing list pgsql-admin

From Nick Fankhauser
Subject Re: Problem with n_distinct being consistently inaccurate.
Date
Msg-id NEBBLAAHGLEEPCGOBHDGKEJAIJAA.nickf@ontko.com
Whole thread Raw
In response to Re: Problem with n_distinct being consistently inaccurate.  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Problem with n_distinct being consistently inaccurate.  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-admin
> It certainly should be the case.  starelid matches to pg_class.oid and
> staattnum matches to pg_attribute.attnum.

My problem was that I was looking up "event_date_time" in pg_class.relname
(and finding it), but the oid matched nothing. when I looked for 'event' in
pg_class & 'event_date_time' in pg_attribute, everything became clear.

So... I updated stadistinct to the actual value of 92,000 as you suggested
and as you predicted, it did not change the plan a bit. I guess I'll look
elsewhere for ways to optimize this query.

Thanks!

-Nick



pgsql-admin by date:

Previous
From: "scott.marlowe"
Date:
Subject: Re: help needed!!!
Next
From: "Mark Carew"
Date:
Subject: Re: steps to ensure referential integrity