From: Bill Moran <wmoran@collaborativefusion.com>
To: Kurt Overberg <kurt@hotdogrecords.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Maintenance question / DB size anomaly...
Date: Wed, 20 Jun 2007 09:25:42 -0400
Message-ID: <20070620092542.1f530273.wmoran@collaborativefusion.com> (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>
In response to Kurt Overberg <kurt@hotdogrecords.com>:
> OOooooookaaaaaaaaay. Since the discussion has wandered a bit I just
> wanted to restate things in an effort to clear the problem in my head.
>
> 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. So my question remains:
Apologies, I must have misunderstood some previous message.
> Its it okay to dump and recreate that index (or reindex it) while the
> servers are down and the database is not being accessed?
There are people here who know _way_ more than me -- but I can't see any
reason why you couldn't just REINDEX it while everything is running. There
may be some performance slowdown during the reindex, but everything should
continue to chug along. A drop/recreate of the index should be OK as well.
> Tom, Bill, Chris and Richard, thank you so much for your thoughts on
> this matter so far. It helps to not feel "so alone" when dealing
> with difficult issues (for me anyway) on a system I don't know so
> much about.
:D Isn't Open Source great!
--
Bill Moran
Collaborative Fusion Inc.
http://people.collaborativefusion.com/~wmoran/
wmoran@collaborativefusion.com
Phone: 412-422-3463x4023
****************************************************************
IMPORTANT: This message contains confidential information and is
intended only for the individual named. If the reader of this
message is not an intended recipient (or the individual
responsible for the delivery of this message to an intended
recipient), please be advised that any re-use, dissemination,
distribution or copying of this message is prohibited. Please
notify the sender immediately by e-mail if you have received
this e-mail by mistake and delete this e-mail from your system.
E-mail transmission cannot be guaranteed to be secure or
error-free as information could be intercepted, corrupted, lost,
destroyed, arrive late or incomplete, or contain viruses. The
sender therefore does not accept liability for any errors or
omissions in the contents of this message, which arise as a
result of e-mail transmission.
****************************************************************
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: wmoran@collaborativefusion.com, kurt@hotdogrecords.com
Subject: Re: Maintenance question / DB size anomaly...
In-Reply-To: <20070620092542.1f530273.wmoran@collaborativefusion.com>
* 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