From: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
---|---|
To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
Cc: | anj patnaik <patna73(at)gmail(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: get this warning from pgAdmin |
Date: | 2015-11-12 19:01:29 |
Message-ID: | CAECtzeVqrZQSatiHegx8DaD9p2KFSWqzed2j2sPiEqd5c+1GGg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
2015-11-12 19:43 GMT+01:00 Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>:
> On 11/12/2015 10:02 AM, anj patnaik wrote:
>
>> I get this warning when trying to fetch data for a postgres db. Does
>> this indicate a real issue? Thanks
>>
>
> Well it means the statistics for the table are out of touch with reality.
> The database will not fall over, but your queries against the table will be
> using stale statistics when the query planner sets up the query.
>
>
>> Running VACUUM recommended
>> The estimated rowcount on the table "recorder" deviates significantly
>> from the actual rowcount. You should run VACUUM ANALYZE on this table.
>>
>
> I would take the suggestion, or you can wait till autovacuum hits the
> table.
>
>
AFAIK, this part of the code in pgAdmin hasn't been touched since quite a
few years. You shouldn't rely on it to know which tables need a VACUUM or
an ANALYZE.
--
Guillaume.
http://blog.guillaume.lelarge.info
http://www.dalibo.com
From | Date | Subject | |
---|---|---|---|
Next Message | John McKown | 2015-11-12 19:16:52 | Re: can postgres run well on NFS mounted partitions? |
Previous Message | Melvin Davidson | 2015-11-12 18:59:47 | Re: get this warning from pgAdmin |