From: | "Albe Laurenz" <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
---|---|
To: | "Simon Windsor *EXTERN*" <simon(dot)windsor(at)cornfield(dot)me(dot)uk>, <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Large Objects and and Vacuum |
Date: | 2012-01-03 11:12:47 |
Message-ID: | D960CB61B694CF459DCFB4B0128514C20749D1BF@exadv11.host.magwien.gv.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Simon Windsor wrote:
[pg_largeobject keeps growing]
> The data only has to be kept for a few days, and generally the system
is
> performing well, but as stated in the email, regular use of vacuumlo,
vacuum
> and autovacuum leaves the OS disc space slowly shrinking.
>
> As a last resort this week, I'm going to get 500+GB of extra file
store
> added, add a tablespace and move pg_largeobjects to this area. Then
use
> CLUSTER to rebuild pg_largeobjects back in the default tablespace.
This
> should fix things I hope, and if needed I'll use Cluster regularly.
You did not pay attention.
Did you verify that large objects actually get deleted in your system?
If not, no magic will ever make pg_largeobject shrink.
In current PostgreSQL, CLUSTER essentially does the same as VACUUM FULL.
Yours,
Laurenz Albe
From | Date | Subject | |
---|---|---|---|
Next Message | Albe Laurenz | 2012-01-03 11:22:52 | Re: asynchronous api questions |
Previous Message | John R Pierce | 2012-01-03 10:34:45 | Re: Adding German Character Set to PostgresSQL |