Re: How to optimize PostgreSQL database size

From: Jim Nasby <jnasby(at)pervasive(dot)com>
To: Qingqing Zhou <zhouqq(at)cs(dot)toronto(dot)edu>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: How to optimize PostgreSQL database size
Date: 2006-06-22 19:44:32
Message-ID: 31F92A9B-2EEE-450D-BEBF-7BB6CA175099@pervasive.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Jun 18, 2006, at 10:47 PM, Qingqing Zhou wrote:
> ""Linux Portal"" <linportal(at)gmail(dot)com> wrote
>> The article on the subject can be read here:
>>
>> http://linux.inet.hr/optimize_postgresql_database_size.html
>>
>
> After dump/restore the database size is 1685 MB and after
> vacuum-full/reindex is 1990 MB. Where we saved 305 MB?

My guess would be due to toasted text columns... does VACUUM FULL
know to vacuum the toast tables only after committing the vacuum on
the base heap?
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message TJ O'Donnell 2006-06-22 19:45:53 aggregate of bitstrings
Previous Message Jim Nasby 2006-06-22 19:34:08 Re: Out of memory error in 8.1.0 Win32