Postgres Pro
Downloads
Home   >   mailing lists

Re: Checkpoint versus Background Writer - Mailing list pgsql-novice

From Shiv Sharma
Subject Re: Checkpoint versus Background Writer
Date
Msg-id CA+LWa-LbEhi-JXqswuMxMAqOeBPvjiNRqjz606LJNGcFt0KAVQ@mail.gmail.com
Whole thread Raw
In response to Re: Checkpoint versus Background Writer  ("SUNDAY A. OLUTAYO" <olutayo@sadeeb.com>)
Responses Re: Checkpoint versus Background Writer  ("SUNDAY A. OLUTAYO" <olutayo@sadeeb.com>)
List pgsql-novice
Tree view
>Checkpoint is different to background writer though works together
>BGW continuously write buffer to disk but checkpoint is interval default to 5min at which the process call >BGW to flush the entire buffer to disk

But with 8.3 and checkpoint_completion_target, is not the checkpoint spread out too? (or can be spread out).



On Fri, Dec 27, 2013 at 10:58 AM, SUNDAY A. OLUTAYO <olutayo@sadeeb.com> wrote:
Checkpoint is different to background writer though works together
BGW continuously write buffer to disk but checkpoint is interval default to 5min at which the process call BGW to flush the entire buffer to disk

Thanks,

Sunday Olutayo


From: "Shiv Sharma" <shiv.sharma.1835@gmail.com>
To: pgsql-novice@postgresql.org
Sent: Friday, December 27, 2013 8:46:42 PM
Subject: [NOVICE] Checkpoint versus Background Writer


They seem to do similar things: clear dirty buffers from shared_buffers to disk.

So why have 2 processes with seperate semantics (seperate set of config partms) ?

Assuming PG is multi-threaded, can't we simply have multiple threads of the checkpoint achieve the same result as (checkpoint + bg)


Shiv


pgsql-novice by date:

Previous
From: "SUNDAY A. OLUTAYO"
Date:
Subject: Re: Checkpoint versus Background Writer
Next
From: "SUNDAY A. OLUTAYO"
Date:
Subject: Re: Checkpoint versus Background Writer