Search Postgresql Archives

Re: Blocked updates and background writer performance

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: Blocked updates and background writer performance
From: Cory Tucker <cory.tucker@xxxxxxxxx>
Date: Wed, 13 Jan 2016 19:17:47 +0000
In-reply-to: <CALd+dcd7S-iZZH=hNUyzKe_VD9nQA67TRQgkWX69T7-ETCtDdA@mail.gmail.com>

On Wed, Jan 13, 2016 at 9:48 AM Vick Khera <vivek@xxxxxxxxx> wrote:

That was my intuition too. Not enough I/O available from the hardware for the workload requested.

As recommended, log your checkpoints and try tuning them to spread the load.

Thanks guys, will turn on checkpoint logging and try to sniff this out further.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

References:
- Blocked updates and background writer performance
  - From: Cory Tucker
- Re: Blocked updates and background writer performance
  - From: Jeff Janes
- Re: Blocked updates and background writer performance
  - From: Vick Khera

Prev by Date: Re: Function error
Next by Date: pg_dump problem with dropped NOT NULL on child table
Previous by thread: Re: Blocked updates and background writer performance
Next by thread: Moving a large DB (> 500GB) to another DB with different locale
Index(es):
- Date
- Thread

[Index of Archives] [Postgresql Jobs] [Postgresql Admin] [Postgresql Performance] [Linux Clusters] [PHP Home] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Books] [PHP Databases] [Postgresql & PHP] [Yosemite]

Powered by Linux