Skip site navigation (1) Skip section navigation (2)

Re: Load distributed checkpoint

From: "Zeugswetter Andreas ADI SD" <ZeugswetterA(at)spardat(dot)at>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>,"Jim C(dot) Nasby" <jim(at)nasby(dot)net>
Cc: "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com>,"Bruce Momjian" <bruce(at)momjian(dot)us>,"ITAGAKI Takahiro" <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>,"PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Load distributed checkpoint
Date: 2007-01-03 11:18:42
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackerspgsql-patches
> > I believe there's something similar for OS X as well. The question
> > would it be better to do that, or to just delay calling fsync until
> > OS has had a chance to write things out.
> A delay is not going to help unless you can suppress additional writes
> to the file, which I don't think you can unless there's very little
> going on in the database --- dirty buffers have to get written to make
> room for other pages, checkpoint in progress or no.

But checkpoint first writes all dirty pages, so we have more than
pages that can be replaced without a write. Thus we have a window where
we can wait until dirty pages have to be replaced again. Since the
is sleeping until fsync, only pages that have to be replaced will be
Question is, how do we time that window.


In response to

pgsql-hackers by date

Next:From: Zeugswetter Andreas ADI SDDate: 2007-01-03 11:56:11
Subject: Re: effective_cache_size vs units
Previous:From: Mark Cave-AylandDate: 2007-01-03 09:15:41
Subject: Re: WITH support

pgsql-patches by date

Next:From: Simon RiggsDate: 2007-01-03 15:35:44
Subject: Re: [HACKERS] Patch to log usage of temporary files
Previous:From: Peter EisentrautDate: 2007-01-03 08:52:29
Subject: Re: xlog directory at initdb time

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group