I had a similar issue:
Look at your indexes, I'll bet they are growing and not recovering unused
pages.
Consider scheduling the REINDEX command like you do for VACUUM.
Terry Fielder
Network Engineer
Great Gulf Homes / Ashton Woods Homes
terry@greatgulfhomes.com
> -----Original Message-----
> From: pgsql-general-owner@postgresql.org
> [mailto:pgsql-general-owner@postgresql.org]On Behalf Of
> Bjoern Metzdorf
> Sent: Tuesday, June 18, 2002 10:28 AM
> To: pgsql-general@postgresql.org
> Subject: [GENERAL] db grows and grows
>
>
> Hi,
>
> I have a 3 GB (fs based) large pgdata directory. I regularly
> do vacuums
> every 15 minutes and vacuums with analyzing every night.
>
> After dumping the whole db (pg_dump -c db), dropping and
> creating the db,
> reinserting the dump and vacuuming again, my pgdata directory
> only contains
> 1 GB. The dump had no errors, all data has been saved and reinserted.
>
> The xlogs/clogs didnt take up 2 GB, so I am wondering what
> has happened.
>
> Shouldn't the vacuuming take care of this?
>
> A (desired) sideeffect is, that the postmaster runs much
> faster now. Queries
> get executed much faster.
>
> If I compare the relpages from before and after, I see the
> difference there
> also.
>
> Any hints?
>
> Greetings,
> Bjoern
>
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/users-lounge/docs/faq.html
>
