| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
| Cc: | "Neuber, Dirk" <dirk(dot)neuber(at)barco(dot)com>, "Henry, Frank" <frank(dot)henry(at)barco(dot)com>, pgsql-admin(at)postgresql(dot)org, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
| Subject: | Re: Large files in main/base |
| Date: | 2010-07-10 14:54:46 |
| Message-ID: | 15568.1278773686@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Guillaume Lelarge <guillaume(at)lelarge(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Neuber, Dirk | 2010-07-11 12:58:14 | Re: Large files in main/base |
| Previous Message | Greg Smith | 2010-07-10 12:44:35 | Re: High Availability: Hot Standby vs. Warm Standby |