pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Pallav Kalva <pkalva@deg.cc>
To: pgsql-performance@postgresql.org
Subject: Wrong Stats and Poor Performance
Date: Mon, 27 Dec 2004 13:52:27 -0500
Message-ID: <41D059EB.9090201@deg.cc> (raw)

Hi Everybody.

      I have a table in my production database which gets updated 
regularly and the stats on this table in pg_class  are totally wrong.  I 
used to run vacuumdb on the whole database daily once and when i posted 
the same problem of wrong stats in the pg_class most of them from this 
list and also from postgres docs suggested me to run the "vacuum 
analyze" more frequently on this table.

I had a setup a cronjob couple of weeks ago to run vacuum analyze every 
3 hours on this table and still my stats are totally wrong. This is 
affecting the performance of the queries running on this table very badly. 

How can i fix this problem ?  or is this the standard postgres behaviour ?

Here are the stats from the problem table on my production database

 relpages |  reltuples
----------+-------------
   168730 | 2.19598e+06

If i rebuild the same table on dev db and check the stats they are 
totally different, I was hoping that there would be some difference in 
the stats from the production db stats but not at this extent, as you 
can see below there is a huge difference in the stats.

 relpages | reltuples
----------+-----------
    25230 |    341155


Thanks!
Pallav





view thread (5+ messages)  latest in thread

Message-ID: <41D059EB.9090201@deg.cc>
Permalink:  ../41D059EB.9090201@deg.cc/
Also on:    postgresql.org/message-id/41D059EB.9090201@deg.cc

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: pkalva@deg.cc
  Subject: Re: Wrong Stats and Poor Performance
  In-Reply-To: <41D059EB.9090201@deg.cc>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox