Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id C668E9FBA1E for ; Tue, 19 Jun 2007 11:12:23 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 43681-01 for ; Tue, 19 Jun 2007 11:12:20 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 7504F9FBC80 for ; Tue, 19 Jun 2007 11:12:09 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.1/8.14.1) with ESMTP id l5JEC6ak027183; Tue, 19 Jun 2007 10:12:06 -0400 (EDT) To: Kurt Overberg cc: pgsql-performance@postgresql.org Subject: Re: Maintenance question / DB size anomaly... In-reply-to: References: Comments: In-reply-to Kurt Overberg message dated "Tue, 19 Jun 2007 09:57:23 -0400" Date: Tue, 19 Jun 2007 10:12:05 -0400 Message-ID: <27182.1182262325@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200706/342 X-Sequence-Number: 25375 Kurt Overberg writes: > In my investigation of this anomaly, I noticed that the data/ dir on > db1 (the master) is around 60 Gigs. The data directory on the slaves > is around 25Gb. After about 3 months of head scratching, someone on > the irc channel suggested that it may be due to index bloat. This is not something you need to guess about. Compare the table and index sizes, one by one, between the master and slaves. Do a VACUUM VERBOSE on the one(s) that are radically bigger on the master, and look at what it has to say. regards, tom lane