From: | Bruno Wolff III <bruno(at)wolff(dot)to> |
---|---|
To: | Jason Godden <jasongodden(at)optushome(dot)com(dot)au> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Growing Database Size |
Date: | 2003-06-14 13:45:33 |
Message-ID: | 20030614134533.GE27374@wolff.to |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Sat, Jun 14, 2003 at 16:35:16 +1000,
Jason Godden <jasongodden(at)optushome(dot)com(dot)au> wrote:
> Hi All,
>
> I've got a bit of a dilemma with growing database sizes. Before upgrading to
> 7.3.2 my 7.3.0 database had an average size of 1.4-2.0gb. I have a large
> number of LO records in my db and presumed the size growth was because of
> them. However I do have the appropriate trigger functions on my LO records
> to ensure that lo_manage runs to unlink the old reference etc.
>
> Since moving to 7.3.2, even though I VACUUM regularly, my DB size has
> increased to 3.2GB on disk!! The raw data only consumes about 700-900mb so I
> feel that an additional 2.2gb for index and statistics info is a bit much!
> Any clues from the experienced among the group?
>
> PS - strange thing is that even with that huge change on disk PG's performance
You probably want to use a reindex. If you have an index on a column
that only increases or decreases over time, the index won't be able
to use reuse pages that are no longer in use. This is fixed in 7.4.
From | Date | Subject | |
---|---|---|---|
Next Message | Bruno Wolff III | 2003-06-14 13:47:45 | Re: Growing Database Size Solved |
Previous Message | Bruno Wolff III | 2003-06-14 13:39:43 | Re: return records in DB load order?? |