Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id EFC39632A48 for ; Sat, 10 Jul 2010 11:54:57 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 92861-01 for ; Sat, 10 Jul 2010 14:54:48 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by mail.postgresql.org (Postfix) with ESMTP id 97DF9632541 for ; Sat, 10 Jul 2010 11:54:50 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id o6AEskha015569; Sat, 10 Jul 2010 10:54:46 -0400 (EDT) To: Guillaume Lelarge cc: "Neuber, Dirk" , "Henry, Frank" , pgsql-admin@postgresql.org, Scott Marlowe Subject: Re: Large files in main/base In-reply-to: <4C38605A.3010101@lelarge.info> References: <4C38605A.3010101@lelarge.info> Comments: In-reply-to Guillaume Lelarge message dated "Sat, 10 Jul 2010 13:58:18 +0200" Date: Sat, 10 Jul 2010 10:54:46 -0400 Message-ID: <15568.1278773686@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.91 tagged_above=-10 required=5 tests=BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201007/42 X-Sequence-Number: 35061 Guillaume Lelarge writes: > Le 10/07/2010 12:43, Neuber, Dirk a écrit : >>> The exact name of the file might be useful information, too. >> >> It is : postgres/8.3/main/base/16385/2613 > This is a system catalog, pg_largeobject, which holds binary objects. If > you use Large Objects, no wonder this table could be really big. Also worth noting is that there's no automatic deletion mechanism for large objects. It could be that the space is being eaten by LOs that aren't referenced anymore. If so, you should think about applying contrib/lo and/or contrib/vacuumlo to manage your LOs. regards, tom lane