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: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Josh Berkus <josh(at)agliodbs(dot)com>, 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:24:05
Message-ID: 20100415202405.GL7259@alvh.no-ip.org (view raw or flat)
Thread:
Lists: pgsql-performance
Tom Lane wrote:
> Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> > We don't call pollsys anywhere.  Something in Solaris must be doing it
> > under the hood.
> 
> pg_usleep calls select(), and some googling indicates that select() is
> implemented as pollsys() on recent Solaris versions.  So Josh's
> assumption that those are delay calls seems plausible.  But it shouldn't
> be sleeping after each page with normal cost_delay parameters, should it?

Certainly not ... The only explanation would be that the cost balance
gets over the limit very frequently.  So one of the params would have to
be abnormally high (vacuum_cost_page_hit, vacuum_cost_page_miss,
vacuum_cost_page_dirty).

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

In response to

Responses

pgsql-performance by date

Next:From: Josh BerkusDate: 2010-04-15 22:17:22
Subject: Re: Autovaccum with cost_delay does not complete on one solaris 5.10 machine
Previous:From: Tom LaneDate: 2010-04-15 20:14:01
Subject: Re: 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