>> 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.
It's certainly the behavior I'm seeing otherwise. In "normal
operation", the number of pages read between pollsys is consistent with
the vacuum delay settings.
>> But it shouldn't
>> be sleeping after each page with normal cost_delay parameters, should it?
Right, that's why I find this puzzling. If the problem was easier to
reproduce it would be easier to analyze.
> 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).
Nope, all defaults. And, all identical to the other server which is
behaving normally.
Honestly, I mostly posted this in hopes that some other Solaris user
would speak up to having seen the same thing.
--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com
--
Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
