| From: | Peter Geoghegan <peter(at)2ndquadrant(dot)com> |
|---|---|
| To: | Jan Wieck <JanWieck(at)yahoo(dot)com> |
| Cc: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Logical to physical page mapping |
| Date: | 2012-10-29 02:50:27 |
| Message-ID: | CAEYLb_Wpvsb3+MQP7WR3fGPrFDWjkrewQb69mbtG+k4fTAejig@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 28 October 2012 22:35, Jan Wieck <JanWieck(at)yahoo(dot)com> wrote:
> The amount of WAL generated with full_page_writes=on is quite substantial.
> For pgbench for example the ratio 20:1. Meaning with full_page_writes you
> write 20x the amount you do without.
Sure, but as always, pgbench pessimises everything by having writes
follow a uniform distribution, which is completely unrepresentative of
the natural world. This will literally maximise the number of pristine
full page images that need to be included. The actual frequency of
checkpoints is a crucial factor here too, and you didn't mention
anything about that.
--
Peter Geoghegan http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training and Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jan Wieck | 2012-10-29 03:39:11 | Re: Logical to physical page mapping |
| Previous Message | Michael Paquier | 2012-10-28 23:48:56 | Re: Creating indexes in the background |