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

Re: Large pgstat.stat file causes I/O storm

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Cristian Gafton <gafton(at)rpath(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Large pgstat.stat file causes I/O storm
Date: 2008-01-29 19:20:45
Message-ID: 24305.1201634445@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Cristian Gafton <gafton(at)rpath(dot)com> writes:
> Autovacuum is disabled, since the database is mostly read only. There is a 
> "vacuumdb -a -z" running nightly on the box. However, the application that 
> queries it does a lot of work with temporary tables - would those bloat 
> the stats at all?

Conceivably, if you mean a lot of short-lived tables rather than a lot
of operations on a few tables.  However, I'd think that would result in
a steady accumulation of stats entries, not a sudden jump as you seemed
to describe.

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Cristian GaftonDate: 2008-01-29 19:45:38
Subject: Re: Large pgstat.stat file causes I/O storm
Previous:From: Tom LaneDate: 2008-01-29 19:09:13
Subject: Re: [PATCHES] Proposed patch: synchronized_scanning GUCvariable

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