pg.ddx.io pgsql-performance@postgresql.org mailing list archive
help / color / mirror / Atom feedautovacuum, any log?
2+ messages / 2 participants
[nested] [flat]
* autovacuum, any log?
@ 2011-12-07 15:34 Anibal David Acosta <aa@devshock.com>
2011-12-07 20:19 ` Re: autovacuum, any log? Scott Marlowe <scott.marlowe@gmail.com>
0 siblings, 1 reply; 2+ messages in thread
From: Anibal David Acosta @ 2011-12-07 15:34 UTC (permalink / raw)
To: pgsql-performance
Hello, I have a postgres 9.0.2 installation.
Every works fine, but in some hours of day I got several timeout in my
application (my application wait X seconds before throw a timeout).
Normally hours are not of intensive use, so I think that the autovacuum
could be the problem.
Is threre any log where autovacuum write information about it self like
"duration for each table" or any other relevante information.
Another inline question, should I exclude bigger tables from autovacuum or
there are some mechanism to tell autovacuum to not run often on bigger
tables (tables with more than 400 millions of rows)
Thanks!
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: autovacuum, any log?
2011-12-07 15:34 autovacuum, any log? Anibal David Acosta <aa@devshock.com>
@ 2011-12-07 20:19 ` Scott Marlowe <scott.marlowe@gmail.com>
0 siblings, 0 replies; 2+ messages in thread
From: Scott Marlowe @ 2011-12-07 20:19 UTC (permalink / raw)
To: Anibal David Acosta <aa@devshock.com>; +Cc: pgsql-performance
On Wed, Dec 7, 2011 at 8:34 AM, Anibal David Acosta <aa@devshock.com> wrote:
> Hello, I have a postgres 9.0.2 installation.
>
> Every works fine, but in some hours of day I got several timeout in my
> application (my application wait X seconds before throw a timeout).
>
> Normally hours are not of intensive use, so I think that the autovacuum
> could be the problem.
>
>
>
> Is threre any log where autovacuum write information about it self like
> “duration for each table” or any other relevante information.
>
>
>
> Another inline question, should I exclude bigger tables from autovacuum or
> there are some mechanism to tell autovacuum to not run often on bigger
> tables (tables with more than 400 millions of rows)
More often than not not the problem will be checkpoint segments not
autovacuum. log vacuum and checkpoints, and then run something like
iostat in the background and keep an eye on %util to see if one or the
other is slamming your IO subsystem. Default tuning for autovac is
pretty conservative, to the point that it won't usually hurt your IO,
but may not keep up with vaccuming, leading to table bloating.
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2011-12-07 20:19 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2011-12-07 15:34 autovacuum, any log? Anibal David Acosta <aa@devshock.com>
2011-12-07 20:19 ` Scott Marlowe <scott.marlowe@gmail.com>
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