From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Kevin Kempter <kevin(at)kevinkempterllc(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: more blob questions |
Date: | 2008-01-18 16:23:32 |
Message-ID: | 9642.1200673412@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Kevin Kempter <kevin(at)kevinkempterllc(dot)com> writes:
> Suppose I have a table with say an integer key, a char column and a large
> object column.
> can I simply delete a row from the table (delete from bigtable where...), then
> run a vacuum (or vacuum full) ? If so, in this scenario will postgres release
> the space back to the OS or must I first remove the large object with
> lo_unlink() ?
That would release only the row's space, not the large object's. You
need to do the lo_unlink().
> also, does the contrib vacuumlo perform tasks I cannot do via vacuum and
> lo_unlink ?
It doesn't do any magic. You might want to read the latest cleaned-up
documentation for it:
http://developer.postgresql.org/pgdocs/postgres/vacuumlo.html
The contrib/lo module is also worth reading about.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | M.Khaled | 2008-01-18 16:42:36 | Can not access the public schema |
Previous Message | Tom Lane | 2008-01-18 15:42:04 | Re: Cannot bind socket |