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

Re: Autovaccum with cost_delay does not complete on one solaris 5.10 machine

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Autovaccum with cost_delay does not complete on one solaris 5.10 machine
Date: 2010-04-15 20:00:56
Message-ID: 20100415200056.GJ7259@alvh.no-ip.org (view raw or flat)
Thread:
Lists: pgsql-performance
Josh Berkus wrote:

> Basically, vacuuming of a table which normally takes about 20 minutes
> interactively with vacuum_cost_delay set to 20 had not completed after
> 14 hours.  When I trussed it, I saw activity which indicated to me that
> autovacuum was doing a pollsys, presumably for cost_limit, every data page.
> 
> Autovacuum was running with vacuum_cost_limit = 200 and
> autovacuum_vacuum_cost_delay = 20, which I believe is the default for 8.3.
> 
> Truss output:
> 
> pollsys(0xFFFFFD7FFFDF83E0, 0, 0xFFFFFD7FFFDF8470, 0x00000000) = 0

So what is it polling?  Please try "truss -v pollsys"; is there a way in
Solaris to report what each file descriptor is pointing to?  (In linux
I'd look at /proc/<pid>/fd)

We don't call pollsys anywhere.  Something in Solaris must be doing it
under the hood.

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

In response to

Responses

pgsql-performance by date

Next:From: Dave CrookeDate: 2010-04-15 20:01:55
Subject: Re: HELP: How to tame the 8.3.x JDBC driver with a biq guery result set
Previous:From: Josh BerkusDate: 2010-04-15 19:44:31
Subject: Autovaccum with cost_delay does not complete on one solaris 5.10 machine

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group