On Wed, Nov 16, 2011 at 4:07 AM, Maksym Boguk <maxim.boguk@gmail.com> wrote:
> Again I not sure it is actual bug or something else go wrong with my
> database.
>
> One of my databases just started produce 256 wal segments in 5 minutes
> instead of 100-200 wal segments per hour (averages).
>
> In the same time write and read activity on DB stay same (according to the
> pg_stat_database data and historical graphs).
> No anti-wraparound vacuum and such things going on.
> Situation staying same during last few days.
>
>
> I found some other anomalies:
> 1)5 minutes after
> SELECT pg_stat_reset_shared('bgwriter');
>
> mirtesen=3D# SELECT * from pg_stat_bgwriter ;
> =A0checkpoints_timed | checkpoints_req | buffers_checkpoint | buffers_cle=
an |
> maxwritten_clean | buffers_backend | buffers_alloc
> -------------------+-----------------+--------------------+--------------=
-+-
> -----------------+-----------------+---------------
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 0 | =A0 =A0 =A0 =A0 =A0 =A0 =A0 2 | =A0 =
=A0 =A0 =A0 =A0 =A0 171675 | =A0 =A0 =A0 =A0 =A0 804 |
> =A0 =A0 =A0 =A0 =A0 =A0 =A00 | =A0 =A0 =A0 =A0 1010429 | =A0 =A0 =A0 1131=
106
> (1 row)
>
> eg almost any new buffer allocated by backend leading to backend write out
> dirty page (and that situation do not change overtime).
This sure sounds like a ring buffer is being used, suggesting VACUUM
or COPY IN activity.
What does pg_stat_activity say?
--=20
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
