Skip site navigation (1) Skip section navigation (2)

Re: Cleaning up large objects

From: "Ole Streicher" <ole-usenet-spam(at)gmx(dot)net>
To: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: Cleaning up large objects
Date: 2004-08-10 15:33:33
Message-ID: 12095.1092152013@www25.gmx.net (view raw or flat)
Thread:
Lists: pgsql-jdbc
I forgot to mention some things:

I use postgreSQL 7.3.2, with the jdbc driver 7.4.

When I execute "vacuum -a -v -z", I get
INFO:  --Relation pg_catalog.pg_largeobject--
INFO:  Index pg_largeobject_loid_pn_index: Pages 41027; Tuples 731708:
Deleted   20.
        CPU 3.95s/0.55u sec elapsed 100.14 sec.
INFO:  Removed 320 tuples in 75 pages.
        CPU 0.02s/0.01u sec elapsed 1.61 sec.
INFO:  Pages 1768741: Changed 14814, Empty 0; Tup 731708: Vac 320, Keep
104534   UnUsed 9314229.
        Total CPU 169.45s/9.47u sec elapsed 737.33 sec.
INFO:  Analyzing pg_catalog.pg_largeobject

320 tuples look like twice the number of large object I just removed. So, I
gues that /something/ works. 
However, no space is freed. Why?

Ole

-- 
NEU: WLAN-Router fr 0,- EUR* - auch fr DSL-Wechsler!
GMX DSL = supergnstig & kabellos http://www.gmx.net/de/go/dsl


In response to

Responses

pgsql-jdbc by date

Next:From: Kris JurkaDate: 2004-08-10 17:38:26
Subject: Re: Cleaning up large objects
Previous:From: Ole StreicherDate: 2004-08-10 15:13:00
Subject: Cleaning up large objects

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group