Skip site navigation (1) Skip section navigation (2)

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search for
  Advanced Search

Re: Vacuum questions...


  • From: Hannu Krosing <hannu(at)skype(dot)net>
  • To: "Joshua D. Drake" <jd(at)commandprompt(dot)com>
  • Cc: "Jim C. Nasby" <jnasby(at)pervasive(dot)com>, pgsql-hackers(at)postgresql(dot)org
  • Subject: Re: Vacuum questions...
  • Date: Sun, 25 Sep 2005 10:03:58 +0300
  • Message-id: <1127631838(dot)4865(dot)49(dot)camel(at)fuji(dot)krosing(dot)net>

On L, 2005-09-24 at 20:25 -0700, Joshua D. Drake wrote:

> Actually this also probably would not gain you much in 8.1
> as vacuum in theory is already dealing with itself.

Interesting. Could you explain it in a more detailed way ?
How does vacuum "deal with itself" in 8.1 ?

> >Also, would it be possible to add some means to check the status of a
> >running vacuum? Even with vacuum verbose, once it starts in on a large
> >table you have no way to know how far along it is.
> >  
> >
> That is an interesting thought... Perhaps a quick scan of
> the table to see how many dead rows there are? Then check
> back every n/10 ? Hmmm... I am not a C guy so I don't know if
> that is technically feasible (although probably possible) but it
> is interesting from a DBA perspective.

Not sure of a "quick scan" approach, espacially for tables big enough
for the progress info would be interesting (in my experience a scan is
never quick).

Perhaps VACUUM could send some statistics after each N pages and this
would then be available through something similar to pg_statistics
table.

-- 
Hannu Krosing <hannu(at)skype(dot)net>




Home | Main Index | Thread Index

Privacy Policy | PostgreSQL Archives hosted by Command Prompt, Inc. | Designed by tinysofa
Copyright © 1996 – 2008 PostgreSQL Global Development Group