| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Tzvetan Tzankov <ceco(at)noxis(dot)net> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: disk space usage enlarging despite vacuuming |
| Date: | 2003-05-25 04:18:25 |
| Message-ID: | 3326.1053836305@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Tzvetan Tzankov <ceco(at)noxis(dot)net> writes:
> only the DB wallet, now is 1.3G !!! after full vacuum and reindexall
> with relation_size from dbsize I got the following things for the system
> tables, wich are not very frustraiting I think
> pg_attribute 11M
> pg_class 8M
> pg_depend 2.5M
> pg_type 1.5M
> (if the returned value is bytes ;-)), I put only the tables that are
> larger then 1M)
> mine tables are also with normal sizes, the sume of them is about 100M
> in this DB there are no large objects at all
Then you've still got about 1.2G left to account for, no?
Have you looked at the sizes of indexes, as opposed to tables?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2003-05-25 05:37:01 | Re: PLPERL |
| Previous Message | Tom Lane | 2003-05-25 03:43:20 | Re: Iterating through individual fields of OLD/NEW records in plpgsql trigger |