2007/7/3, Greg Smith <[EMAIL PROTECTED]>:
On Fri, 29 Jun 2007, Ho Fat Tsang wrote:
> I noticed that for each time the pgsql slow down, there is a short
> period a process called "pdflush" eating up lot of I/O. I've goolgled
> and know it is a process for writing d
2007/6/29, Richard Huxton <[EMAIL PROTECTED]>:
Ho Fat Tsang wrote:
> Hi Richard,
>
>I've tested again according your suggestion. I noticed that for each
> time the pgsql slow down, there is a short period a process called
> "pdflush"
> eating up lot
/28, Kevin Grittner <[EMAIL PROTECTED]>:
>>> On Thu, Jun 28, 2007 at 1:54 AM, in message
<[EMAIL PROTECTED]>, "Ho Fat
Tsang"
<[EMAIL PROTECTED]> wrote:
>
> I don't know why the server occasionally
> slow down a bit for every 3 minutes.
If the
Hi Greg.
2007/6/28, Greg Smith <[EMAIL PROTECTED]>:
On Thu, 28 Jun 2007, Ho Fat Tsang wrote:
> I have tuned the checkpoint_timeout to 30 second which is ten times less
> than default and the issue is still reproduced.
Doing a checkpoint every 30 seconds is crazy; no wonder yo
acuum (a executeable
located in /bin) parallel under normal production load but it seems won't
help.
Thanks for help.
Twinsen
2007/6/28, Richard Huxton <[EMAIL PROTECTED]>:
Ho Fat Tsang wrote:
> Hi Richard,
>
> Thank for your prompt reply. I have used the command "
2 2137 41 7 40
11
As you said, it seems for each 3~4 minutes, there is a I/O peak. But what is
the problem indicating by it ?
Thanks for help.
Twinsen
2007/6/28, Richard Huxton <[EMAIL PROTECTED]>:
Ho Fat Tsang wrote:
> Hi Richard,
>
> I have tuned the checkpoint_timeout
Hi Richard,
I have tuned the checkpoint_timeout to 30 second which is ten times less
than default and the issue is still reproduced. Do you have any recommended
configuration for WAL ?
Thanks
Twinsen
2007/6/28, Richard Huxton <[EMAIL PROTECTED]>:
Ho Fat Tsang wrote:
>
>
Hi,
I am new for postgresql server. And now i work on a projects which
requires postgreSQL 8.0 and Java. I don't know why the server occasionally
slow down a bit for every 3 minutes.
I have changed the log configuration so that it logs all statement
transaction > 1000 ms and the result shown be
