On May 5, 3:37 pm, j...@commandprompt.com ("Joshua D. Drake") wrote:
> On Wed, 2010-05-05 at 09:40 -0700, Nikola wrote:
> > I looked at the pg_class table and noticed that its size is 1010Mb and
> > index size is 1137Mb, while the table itself has only 3615 rows in it.
> > I tried vacuuming it, but that did not change anything. Is there
> > anything I can do to get this table back to the size it is supposed to
> > be at?
>
> > PostgreSQL 8.2.6 on Windows 2003 Server.
>
> vacuum full, its an exclusive lock though.
>
> I don't recall if 8.2 autovacuum would vacuum system catalogs or not.
> Either way, you really should upgrade, especially since you are on
> Windows.
>
> Joshua D. Drake
>
>
>
> --
> PostgreSQL.org Major Contributor
> Command Prompt, Inc:http://www.commandprompt.com/- 503.667.4564
> Consulting, Training, Support, Custom Development, Engineering
>
> --
> Sent via pgsql-general mailing list (pgsql-gene...@postgresql.org)
> To make changes to your
> subscription:http://www.postgresql.org/mailpref/pgsql-general
Yes, I was hoping not to have to do a vacuum full due to the exclusive
lock. However, if that's the only solution (other than upgrading in
general) then that's what needs to happen. Hopefully, vacuum full does
not end up taking an extremely long time to run.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
