| From: | Marti Raudsepp <marti(at)juffo(dot)org> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Greg Smith <greg(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Spread checkpoint sync |
| Date: | 2011-01-16 03:35:17 |
| Message-ID: | AANLkTimG+WgKS8bHUo-wR5cgm2G15nBP9n=yrYf7=SS+@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Jan 15, 2011 at 14:05, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> Idea #4: For ext3 filesystems that like to dump the entire buffer
> cache instead of only the requested file, write a little daemon that
> runs alongside of (and completely indepdently of) PostgreSQL. Every
> 30 s, it opens a 1-byte file, changes the byte, fsyncs the file, and
> closes the file, thus dumping the cache and preventing a ridiculous
> growth in the amount of data to be sync'd at checkpoint time.
Wouldn't it be easier to just mount in data=writeback mode? This
provides a similar level of journaling as most other file systems.
Regards,
Marti
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2011-01-16 04:14:34 | Re: Spread checkpoint sync |
| Previous Message | Andreas Karlsson | 2011-01-16 01:49:55 | Re: Bug in pg_describe_object, patch v2 |