| From: | Devrim GÜNDÜZ <devrim(at)gunduz(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Richard Huxton <dev(at)archonet(dot)com>, PostgreSQL - General ML <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: On-disk size of db increased after restore |
| Date: | 2010-09-01 22:15:37 |
| Message-ID: | 1283379337.2484.30.camel@hp-laptop2.gunduz.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, 2010-09-01 at 16:59 -0400, Tom Lane wrote:
> It would help if Devrim could break down the bloat to the level of
> individual tables/indexes.
While setting up this data (by anonymizing table names, etc), I saw that
almost all relations are smaller on backup server, as compared to prod.
Yeah, there is a little bloat on master, but at the end of the day,
total size is expected to be smaller on backup.
See 5 top disk space eaters (in bytes):
Prod:
idx1|1441636352 bytes
tbl3|3248930816 bytes
tbl4|9065570304 bytes
tbl5|10850549760 bytes
Backup:
idx1|1215463424 bytes
tbl3|3189325824 bytes
tbl4|8910422016 bytes
tbl5|10814955520 bytes
Almost all relations are smaller on backup.
Regards,
--
Devrim GÜNDÜZ
PostgreSQL Danışmanı/Consultant, Red Hat Certified Engineer
PostgreSQL RPM Repository: http://yum.pgrpms.org
Community: devrim~PostgreSQL.org, devrim.gunduz~linux.org.tr
http://www.gunduz.org Twitter: http://twitter.com/devrimgunduz
| From | Date | Subject | |
|---|---|---|---|
| Next Message | z-saito | 2010-09-01 22:27:15 | Re: Problems with ODBC Driver |
| Previous Message | John R Pierce | 2010-09-01 21:52:45 | Re: postgreSQL problem |