From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | Rik Bellens <rik(dot)bellens(at)telin(dot)ugent(dot)be> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: strange table disk sizes |
Date: | 2011-09-01 16:59:54 |
Message-ID: | CAOR=d=22Cn0vJqitKbkXY0eYHo+0M2zB1d9K5c13hjXmS++3qQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, Sep 1, 2011 at 10:04 AM, Rik Bellens <rik(dot)bellens(at)telin(dot)ugent(dot)be> wrote:
>
> after running reindex on the stats_count_pkey, the disk size of this index
> was reduced with about 2 gigs, but the size of the table itself was still
> very large.
> running 'vacuum full' also reduced the table size from 14 gigs to about 2
> gigs.
> I will now regullarly check the database with the mentioned tools and
> queries.
> thank you for the very usefull tips
Excellent. keep in mind that vacuum full on a table can lead to index
bloat, so you might need to reindex after that.
From | Date | Subject | |
---|---|---|---|
Next Message | Jerry LeVan | 2011-09-01 17:07:08 | How can I merge two tables? |
Previous Message | Merlin Moncure | 2011-09-01 16:22:31 | Re: md5 of table |