X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id D282AEAE4AC for ; Sat, 23 Oct 2004 03:50:49 +0100 (BST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 37842-10 for ; Sat, 23 Oct 2004 02:50:51 +0000 (GMT) Received: from stubee.d2hosting.net (d2hosting.net [66.70.41.160]) by svr1.postgresql.org (Postfix) with ESMTP id B51B9EAE488 for ; Sat, 23 Oct 2004 03:50:39 +0100 (BST) Received: from [127.0.0.1] (stubee.d2hosting.net [66.70.41.160]) by stubee.d2hosting.net (8.11.6/linuxconf) with ESMTP id i9N2onf25658; Fri, 22 Oct 2004 21:50:49 -0500 Message-ID: <4179C703.9060603@idigx.com> Date: Fri, 22 Oct 2004 21:50:43 -0500 From: Thomas Swan User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tom Lane Cc: Francesco.Borgoglio@cedacri.it, pgsql-admin@postgresql.org Subject: Re: About System Catalogs References: <19253.1098402901@sss.pgh.pa.us> In-Reply-To: <19253.1098402901@sss.pgh.pa.us> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: multipart/alternative; boundary="------------070108030506010404020305" X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.8 tagged_above=0.0 required=5.0 tests=HTML_30_40, HTML_MESSAGE X-Spam-Level: X-Archive-Number: 200410/314 X-Sequence-Number: 15307 This is a multi-part message in MIME format. --------------070108030506010404020305 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Tom Lane wrote: >Francesco.Borgoglio@cedacri.it writes: > > >>2) As i had a very large pg_largeogject, i deleted rows e now i have a >>clean, small table. >> The table is empty but its index pg_largeogject_loid_pn_index lasts >>to retain a lot of bytes. >> >> > >REINDEX should fix this. > > > Is REINDEX still going to be a necessity in the 8.0 release? I remembered at there was a discussion on the mailing list about a fix or need to fix VACUUM so that manually reindexing would not be necessary... --------------070108030506010404020305 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Tom Lane wrote:
Francesco.Borgoglio@cedacri.it writes:
  
2) As i had a very large pg_largeogject, i deleted rows e now i have a 
clean, small table.
    The table is empty but its index  pg_largeogject_loid_pn_index  lasts 
to retain a lot of bytes.
    

REINDEX should fix this.

  
Is REINDEX still going to be a necessity in the 8.0 release?  I remembered at there was a discussion on the mailing list about a fix or need to fix VACUUM so that manually reindexing would not be necessary...

--------------070108030506010404020305--