| From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Postgres hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Double-writes, take two? |
| Date: | 2018-04-18 09:40:51 |
| Message-ID: | alpine.DEB.2.20.1804181135520.8472@lancre |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bonjour Michaël,
> - double-write buffers use a pre-decided numbers of pages (32 for the
> checkpointer, 128 divided into 4 buckets for the backends), which are
> synced into disk once each batch is full.
> - The double-write file of the checkpointer uses ordering of pages using
> blocks number and files to minimize the number of syncs to happen, using
> a custom sequential I/O algorithm.
I'm not sure from reading the descriptions.
Are these particular features related/similar to 9cd00c4 "Checkpoint
sorting and balancing" and 428b1d6 "Allow to trigger kernel writeback
after a configurable number of writes", committed in February 2016?
--
Fabien.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2018-04-18 09:52:01 | Re: Fix for documentation of Covering Indexes |
| Previous Message | Ashutosh Bapat | 2018-04-18 09:36:42 | Re: Should we add GUCs to allow partition pruning to be disabled? |