From: | Mike Baker <bakerlmike(at)yahoo(dot)com> |
---|---|
To: | pgsql-admin(at)postgresql(dot)org |
Subject: | Vacuum Question |
Date: | 2002-12-16 15:52:19 |
Message-ID: | 20021216155219.87183.qmail@web13807.mail.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Hi.
I am running a weekly cron job to vacuum our
production database. Everything seems to look OK,
except for the report around the pg_largeobjects
table. I was wondering if there is some tunning that I
need to do to my database, or if it is normal to have
so many tuples and deletes for pg_largeobjects. Here
is the output:
VACUUM
--Relation pg_largeobject--
Pages 409852: Changed 6205, reaped 393786, Empty 0,
New 0; Tup 1287298: Vac 14028, Keep/VTL 0/0, Crash 0,
UnUsed 454755, MinLen 45, MaxLen 2092; Re-using:
Free/Avail. Space 716319960/716272248; EndEmpty/Avail.
Pages 0/391372. CPU 17.65s/1.09u sec.
Index pg_largeobject_loid_pn_index: Pages 13833;
Tuples 1287298: Deleted 14028. CPU 0.65s/1.99u sec.
Rel pg_largeobject: Pages: 409852 --> 407718; Tuple(s)
moved: 4278. CPU 64.96s/194.85u sec.
Index pg_largeobject_loid_pn_index: Pages 13833;
Tuples 1287298: Deleted 4278. CPU 0.45s/0.68u sec.
Analyzing..
Thanks
Mike Baker
SCM Labs, Inc.
__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
From | Date | Subject | |
---|---|---|---|
Next Message | Justin Georgeson | 2002-12-16 19:06:18 | Re: pg_dumpall doesn't work |
Previous Message | Ganesh Rajan | 2002-12-16 13:16:44 | hello gurus |