Re: frustration with database size <long>

Thanks! I must have missed dropping/recreating one of
the primary key indexes. The relpages for the index
exceeded the relpages for the table.

I dropped and recreated the index, and vacuumed the
database. The overall database size is down to 11GB.
It's still large; but at least the numbers make more
sense.

Thanks again,

Andrew Gould

--- Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Andrew Gould <andrewgould(at)yahoo(dot)com> writes:
> > The process above resulted in an **increase** in
> > database size from 12GB to 14GB.
> > I'm both surprised and stumped.
>
> Seems odd to me too. Like Einar, I am wondering
> about index sizes.
>
> An easy way to get some data is to do a VACUUM so
> that the relpages
> statistics are up to date, and then do
>
> select relname,relkind,relpages from pg_class order
> by relpages desc;
>
> regards, tom lane
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/users-lounge/docs/faq.html

__________________________________________________
Do You Yahoo!?
Send FREE video emails in Yahoo! Mail!
http://promo.yahoo.com/videomail/