Postgres Pro
Downloads
Home   >   mailing lists

Re: get this warning from pgAdmin - Mailing list pgsql-general

From Melvin Davidson
Subject Re: get this warning from pgAdmin
Date
Msg-id CANu8FiyqegZ9G0gH-BXf+qOZ7f5xpN+Zp5N8_VXzCD2gV1yAxg@mail.gmail.com
Whole thread Raw
In response to get this warning from pgAdmin  (anj patnaik <patna73@gmail.com>)
List pgsql-general
Tree view
This is not necessarily a major issue. It is simply an advisory that a significant number of rows in the table have been inserted, updated or deleted and that in order to have reliable statistics, a vacuum analyze should be done.

Depending on the number of rows in the table and the difference between actual row count and and the current statistics row count, you can decide if you need to vacuum  analyze or delay.

One rule of thumb is to consider the response time of queries against that tablet. IOW, are DML queries involving that table completing within a couple of seconds? If yes, you can delay a while or wait for autovacuum to be done on that table. If the DML is taking more than a few seconds, then yes, it is advisable to vacuum analyze it.

On Thu, Nov 12, 2015 at 1:02 PM, anj patnaik <patna73@gmail.com> wrote:
I get this warning when trying to fetch data for a postgres db. Does this indicate a real issue? Thanks

Running VACUUM recommended
The estimated rowcount on the table "recorder" deviates significantly from the actual rowcount. You should run VACUUM ANALYZE on this table. 



--
Melvin Davidson
I reserve the right to fantasize.  Whether or not you
wish to share my fantasy is entirely up to you.

pgsql-general by date:

Previous
From: Scott Marlowe
Date:
Subject: Re: can postgres run well on NFS mounted partitions?
Next
From: Guillaume Lelarge
Date:
Subject: Re: get this warning from pgAdmin