pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Charles.Hou <ivan.hou@msa.hinet.net>
To: pgsql-admin@postgresql.org
Subject: Re: the right time to vacuum database?
Date: Thu, 07 Jun 2007 00:07:03 -0700
Message-ID: <1181200023.281625.249120@n15g2000prd.googlegroups.com> (raw)
In-Reply-To: <20070606195101.GF11545@phlogiston.dyndns.org>
References: <1181039589.643323.59660@r19g2000prf.googlegroups.com>
	<20070605132546.GI4818@phlogiston.dyndns.org>
	<1181089690.963738.260660@n15g2000prd.googlegroups.com>
	<20070606195101.GF11545@phlogiston.dyndns.org>

On 6 7 ,   3 51 , a...@crankycanuck.ca (Andrew Sullivan) wrote:
> On Tue, Jun 05, 2007 at 05:28:10PM -0700, Charles.Hou wrote:
> > Client connected: about 100 pc, 1 pc with 1 connection at least, the
> > max is 4 connections
>
> So up to 400 connections?  Are they all running transactions?  For
> any length of time?
>
> > 194 tables on the database, and some of the tables  always executed
> > the update/insert command .
>
> So _some_ tables are getting updated?  (Inserts are not really
> relevant to vacuuming here, but they'll surely be relevant to size)
>
> > i also set the autovacuum to enable. today, the database size is
> > 497MB. 497-440MB=57MB, 57 MB have been increased in 18  hours.
> > what's wrong with my PostgreSql Server?
>
> Maybe nothing.  How much data do you think you're putting in there?
> What does VACUUM VERBOSE say, as I asked about -- are you getting a
> lot of dead space?  
>
i use the VACUUM VERBOSE a table , but it had been hold 10 minutes . i
must use the linux command " kill " to exit the VACUUM.
after i kill this PID, the PostgreSql have been restart
automatically.

and vacuum result of the other table

INFO:  vacuuming "public.trade_rpt"
INFO:  "ftrade_rpt": found 987 removable, 117279 nonremovable row
versions in 16875 pages
DETAIL:  0 dead row versions cannot be removed yet.
Nonremovable row versions range from 324 to 1280 bytes long.
There were 9 unused item pointers.
Total free space (including removable row versions) is 9059076 bytes.
138 pages are or will become empty, including 0 at the end of the
table.
15838 pages containing 8772044 free bytes are potential move
destinations.
CPU 0.01s/0.00u sec elapsed 341.61 sec.

341.61sec???




view thread (15+ messages)  latest in thread

Message-ID: <1181200023.281625.249120@n15g2000prd.googlegroups.com>
Permalink:  ../1181200023.281625.249120@n15g2000prd.googlegroups.com/
Also on:    postgresql.org/message-id/1181200023.281625.249120@n15g2000prd.googlegroups.com

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: ivan.hou@msa.hinet.net, pgsql-admin@postgresql.org
  Subject: Re: the right time to vacuum database?
  In-Reply-To: <1181200023.281625.249120@n15g2000prd.googlegroups.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox