From: Joshua D. Drake <jd@commandprompt.com>
To: Josh Berkus <josh@agliodbs.com>
Cc: Cédric Villemain <cedric.villemain.debian@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Write-heavy pg_stats_collector on mostly idle server
Date: Mon, 07 Feb 2011 15:12:36 -0800
Message-ID: <1297120356.18411.197.camel@jd-desktop> (raw)
In-Reply-To: <4D507920.2030909@agliodbs.com>
References: <4D4C4E15.20401@agliodbs.com>
<AANLkTinpWWrDHR9KJNebgtbvpXpL4UdQszD0GxF+FWWu@mail.gmail.com>
<4D507920.2030909@agliodbs.com>
On Mon, 2011-02-07 at 14:58 -0800, Josh Berkus wrote:
> >> Anyone seen anything like this before?
> >>
> >
> > it is the expected behavior, IIRC
>
> OK. It just seems kind of pathological for stats file writing to be 10X
> the volume of data writing. I see why it's happening, but I think it's
> something we should fix.
I don't think it is expected. As I recall, it is something we fixed a
couple of major versions back (8.2?). It used to be that stats would
write every 500ms. We changed that to when they are asked for (via a
select from the table or something). Specifically because it could cause
this type of problem.
Am I thinking of something else?
I remember going back and forth with tgl about this, tgl?
JD
>
> --
> -- Josh Berkus
> PostgreSQL Experts Inc.
> http://www.pgexperts.com
>
--
PostgreSQL.org Major Contributor
Command Prompt, Inc: http://www.commandprompt.com/ - 509.416.6579
Consulting, Training, Support, Custom Development, Engineering
http://twitter.com/cmdpromptinc | http://identi.ca/commandprompt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: jd@commandprompt.com, josh@agliodbs.com, cedric.villemain.debian@gmail.com
Subject: Re: Write-heavy pg_stats_collector on mostly idle server
In-Reply-To: <1297120356.18411.197.camel@jd-desktop>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
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