From: | "Inaam Rana" <inaamrana(at)gmail(dot)com> |
---|---|
To: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
Cc: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Kevin Grittner" <Kgrittn(dot)CCAP(dot)Courts(at)wicourts(dot)gov>, "Jim C(dot) Nasby" <jim(at)nasby(dot)net>, "ITAGAKI Takahiro" <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Load distributed checkpoint |
Date: | 2006-12-10 14:49:08 |
Message-ID: | 833c669b0612100649k5cba78f7w4b3dd15203367851@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
> Unless PostgreSQL gets much closer to the hardware than the community
> consensus seems to support, I don't understand what you could do in the
> checkpoint phase that would improve on that. (That, of course, doesn't
> mean I'm not missing something, just that the arguments made so far
> haven't shown me that the suggested changes would do anything but move
> the problem around a little bit.)
If we can try out things like O_SYNC and/or O_DIRECT that will give us
exact information about dirty pages that need be written to the disk at any
given point in time. We can then use this information to design light weight
checkpoints.
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Fuhr | 2006-12-10 14:53:36 | Re: psql display of Unicode combining characters in 8.2 |
Previous Message | Neil Conway | 2006-12-10 14:28:23 | Re: EXPLAIN ANALYZE |
From | Date | Subject | |
---|---|---|---|
Next Message | Devrim GUNDUZ | 2006-12-10 16:44:04 | Re: 8.2.0 pdf |
Previous Message | Simon Riggs | 2006-12-10 12:57:01 | Re: [HACKERS] Configuring BLCKSZ and XLOGSEGSZ (in 8.3) |