Received: from localhost (postgresql.org [64.49.215.8])
	by postgresql.org (Postfix) with ESMTP id DD536476000
	for <pgsql-admin@postgresql.org>; Mon, 16 Dec 2002 10:52:37 -0500 (EST)
Received: from web13807.mail.yahoo.com (web13807.mail.yahoo.com
	[216.136.175.17])
	by postgresql.org (Postfix) with SMTP id 14CC7476315
	for <pgsql-admin@postgresql.org>; Mon, 16 Dec 2002 10:52:15 -0500 (EST)
Message-ID: <20021216155219.87183.qmail@web13807.mail.yahoo.com>
Received: from [65.101.243.177] by web13807.mail.yahoo.com via HTTP;
	Mon, 16 Dec 2002 07:52:19 PST
Date: Mon, 16 Dec 2002 07:52:19 -0800 (PST)
From: Mike Baker <bakerlmike@yahoo.com>
Subject: Vacuum Question
To: pgsql-admin@postgresql.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Virus-Scanned: by AMaViS new-20020517
X-Archive-Number: 200212/199
X-Sequence-Number: 6694

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