From: Tom Lane <tgl@sss.pgh.pa.us>
To: Guillaume Lelarge <guillaume@lelarge.info>
Cc: Neuber, Dirk <dirk.neuber@barco.com>
Cc: Henry, Frank <frank.henry@barco.com>
Cc: pgsql-admin@postgresql.org, Scott Marlowe <scott.marlowe@gmail.com>
Subject: Re: Large files in main/base
Date: Sat, 10 Jul 2010 10:54:46 -0400
Message-ID: <15568.1278773686@sss.pgh.pa.us> (raw)
In-Reply-To: <4C38605A.3010101@lelarge.info>
References: <ED2EA636E2C9744A96B417491D4793BB07E00D3D@KUUMEX03.barco.com>
<4C38605A.3010101@lelarge.info>
Guillaume Lelarge <guillaume@lelarge.info> 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
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-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, guillaume@lelarge.info, dirk.neuber@barco.com, frank.henry@barco.com, scott.marlowe@gmail.com
Subject: Re: Large files in main/base
In-Reply-To: <15568.1278773686@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