Re: Cleaning up large objects
| От | Ole Streicher |
|---|---|
| Тема | Re: Cleaning up large objects |
| Дата | |
| Msg-id | 12095.1092152013@www25.gmx.net обсуждение |
| Ответ на | Cleaning up large objects ("Ole Streicher" <ole-usenet-spam@gmx.net>) |
| Ответы |
Re: Cleaning up large objects
|
| Список | 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 f�r 0,- EUR* - auch f�r DSL-Wechsler!
GMX DSL = superg�nstig & kabellos http://www.gmx.net/de/go/dsl
В списке pgsql-jdbc по дате отправления: