pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Matthew T. O'Connor <matthew@zeut.net>
To: Steve Crawford <scrawford@pinpointresearch.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Excessive growth of pg_attribute and other system tables
Date: Mon, 21 Mar 2005 13:52:07 -0500
Message-ID: <423F17D7.7040904@zeut.net> (raw)
In-Reply-To: <200503171536.10389.scrawford@pinpointresearch.com>
References: <200503171515.38214.scrawford@pinpointresearch.com>
	<200503171536.10389.scrawford@pinpointresearch.com>

Steve Crawford wrote:

>On Thursday 17 March 2005 3:15 pm, Steve Crawford wrote:
>  
>
>>I'm having trouble with physical growth of postgresql system
>>tables....
>>    
>>
>
>Additional info. The most recent autovacuum entries for the 
>pg_attribute table are: 
>
>[2005...] Performing: VACUUM ANALYZE "pg_catalog"."pg_attribute"
>[2005...]   table name: tati."pg_catalog"."pg_attribute"
>[2005...]      relid: 1249;   relisshared: 0
>[2005...]      reltuples: 9334.000000;  relpages: 82282
>[2005...]      curr_analyze_count: 6647115; curr_vacuum_count: 861454
>[2005...]      last_analyze_count: 6647115; last_vacuum_count: 861454
>[2005...]      analyze_threshold: 9834; vacuum_threshold: 19668
>
>and
>
>[2005...] Performing: ANALYZE "pg_catalog"."pg_attribute"
>[2005...]   table name: foo."pg_catalog"."pg_attribute"
>[2005...]      relid: 1249;   relisshared: 0
>[2005...]      reltuples: 4843240.000000;  relpages: 82284
>[2005...]      curr_analyze_count: 6657041; curr_vacuum_count: 862897
>[2005...]      last_analyze_count: 6657041; last_vacuum_count: 861454
>[2005...]      analyze_threshold: 4843740; vacuum_threshold: 19668
>
>(Both within past 1 day - dates truncated to avoid line-wrap.) The 
>table currently has just over 9,000 tuples and I have no reason to 
>believe that should have changed substantially. The thresholds and 
>counts seem way off - especially in the second pass.
>  
>

I believe this discrepancy has to do with the fact that ANALYZE can 
return some very bogus values for reltuples, where as vacuum always 
returns an accurate count.  I'm not sure how to best handle this.




view thread (19+ messages)  latest in thread

Message-ID: <423F17D7.7040904@zeut.net>
Permalink:  ../423F17D7.7040904@zeut.net/
Also on:    postgresql.org/message-id/423F17D7.7040904@zeut.net

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: matthew@zeut.net, scrawford@pinpointresearch.com
  Subject: Re: Excessive growth of pg_attribute and other system tables
  In-Reply-To: <423F17D7.7040904@zeut.net>
  References: <200503171515.38214.scrawford@pinpointresearch.com> <200503171536.10389.scrawford@pinpointresearch.com> <423F17D7.7040904@zeut.net>

* 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