pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Kurt Overberg <kurt@hotdogrecords.com>
Cc: Chris Browne <cbbrowne@acm.org>
Cc: pgsql-performance@postgresql.org
Subject: Re: Maintenance question / DB size anomaly...
Date: Wed, 20 Jun 2007 11:22:37 -0400
Message-ID: <18180.1182352957@sss.pgh.pa.us> (raw)
In-Reply-To: <E5281888-721F-441C-9DC3-40EEFF4A4952@hotdogrecords.com>
References: <A6D35557-74A3-47CF-B426-143C8CE01A13@hotdogrecords.com>
	<607iq0dlns.fsf@dba2.int.libertyrms.com>
	<1FF54A1D-9085-4C9B-81F3-D860FB132D44@hotdogrecords.com>
	<16441.1182288819@sss.pgh.pa.us>
	<A0763165-9B49-42C7-BBE7-4A670D74B7EE@hotdogrecords.com>
	<18495.1182295570@sss.pgh.pa.us>
	<4D1C51F2-79EA-4468-BF2D-1D5591BD8A3D@hotdogrecords.com>
	<1876.1182307875@sss.pgh.pa.us>
	<E5281888-721F-441C-9DC3-40EEFF4A4952@hotdogrecords.com>

Kurt Overberg <kurt@hotdogrecords.com> writes:
> Okay, so the sl_log_1 TABLE looks okay.  Its the indexes that seem to  
> be messed up, specifically sl_log_1_idx1 seems to think that there's
>>> 300,000 rows in the table its associated with.  I just want to fix  
> the index, really.

I'm not sure how you arrive at that conclusion.  The VACUUM VERBOSE
output you provided here:
http://archives.postgresql.org/pgsql-performance/2007-06/msg00370.php
shows clearly that there are lots of rows in the table as well as
the indexes.  A REINDEX would certainly cut the size of the indexes
but it isn't going to do anything about the extraneous rows.

When last heard from, you were working on getting pg_filedump output for
some of the bogus rows --- what was the result?

			regards, tom lane



view thread (23+ messages)  latest in thread

Message-ID: <18180.1182352957@sss.pgh.pa.us>
Permalink:  ../18180.1182352957@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/18180.1182352957@sss.pgh.pa.us

 · 

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: tgl@sss.pgh.pa.us, kurt@hotdogrecords.com, cbbrowne@acm.org
  Subject: Re: Maintenance question / DB size anomaly...
  In-Reply-To: <18180.1182352957@sss.pgh.pa.us>

* 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