1:56 AM
> To: Tom Lane
> Cc: pgsql-admin
> Subject: Re: [ADMIN] Problem with pgstat timneouts
>
> checkpoint_segments = 1024 # in logfile segments, min 1,
> 16MB each
> checkpoint_timeout = 60min # range 30s-1h
> checkpoint_completion_target = 0
the insertion of the
data, in which records are inserted and deleted - never updated.
> -Original Message-
> From: Tom Lane [mailto:t...@sss.pgh.pa.us]
> Sent: Thursday, December 22, 2011 11:45 AM
> To: Benjamin Krajmalnik
> Cc: pgsql-admin
> Subject: Re: [ADMIN] Proble
"Benjamin Krajmalnik" writes:
> The only thing which I see when I run iostat is load on the drives every
> so often. Mifd0 is the database, mifd1 is the pg_xlog.
Hmm. Maybe checkpoints or something else saturating your drives for a
little while? You might want to be more aggressive about smoot
Original Message-
> From: Tom Lane [mailto:t...@sss.pgh.pa.us]
> Sent: Thursday, December 22, 2011 10:55 AM
> To: Benjamin Krajmalnik
> Cc: pgsql-admin
> Subject: Re: [ADMIN] Problem with pgstat timneouts
>
> "Benjamin Krajmalnik" writes:
> > About a month
"Benjamin Krajmalnik" writes:
> About a month ago, I started receiving quite a few pgstat timeouts on my
> production database.
> PostgreSQL 9.0.3 on amd64-portbld-freebsd8.1, compiled by GCC cc (GCC)
> 4.2.1 20070719 [FreeBSD], 64-bit
> I am not sure where to start looking for the cause.
Yeah
About a month ago, I started receiving quite a few pgstat timeouts on my
production database.
PostgreSQL 9.0.3 on amd64-portbld-freebsd8.1, compiled by GCC cc (GCC)
4.2.1 20070719 [FreeBSD], 64-bit
I am not sure where to start looking for the cause.
Database has been up since march without any
