From: | Andreas Joseph Krogh <andreas(at)visena(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: How to keep pg_largeobject from growing endlessly |
Date: | 2015-04-15 14:22:16 |
Message-ID: | VisenaEmail.2a.4bf3500b326abd8e.14cbd73f6f8@tc7-visena |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
På onsdag 15. april 2015 kl. 16:05:22, skrev Adam Hooper <adam(at)adamhooper(dot)com
<mailto:adam(at)adamhooper(dot)com>>: On Wed, Apr 15, 2015 at 9:57 AM, Andreas Joseph
Krogh
<andreas(at)visena(dot)com> wrote:
>
> På onsdag 15. april 2015 kl. 15:50:36, skrev Adam Hooper
<adam(at)adamhooper(dot)com>:
>
> On Wed, Apr 15, 2015 at 4:49 AM, Andreas Joseph Krogh
> <andreas(at)visena(dot)com> wrote:
> >
> > In other words: Does vacuumlo cause diskspace used by pg_largeobject to
be freed to the OS (after eventually vacuumed by autovacuum)?
>
> No.
>
> Ok. Out of curiousity; When does it get freed, when VACUUM FULL'ed?
Yes. VACUUM FULL or CLUSTER will free the space. (Of course, you need
a lot of free disk space to perform those operations.) I'm sure there's a
good reason for why VACUUM FULL needs to rewreite the whole table and cannot
"just free the unused space to the OS". -- Andreas Joseph Krogh CTO / Partner
- Visena AS Mobile: +47 909 56 963 andreas(at)visena(dot)com
<mailto:andreas(at)visena(dot)com> www.visena.com <https://www.visena.com>
<https://www.visena.com>
From | Date | Subject | |
---|---|---|---|
Next Message | Pawel Veselov | 2015-04-15 18:19:11 | Re: Help with slow table update |
Previous Message | Igor Neyman | 2015-04-15 14:14:10 | Re: Help with slow table update |