| From: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> |
|---|---|
| To: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: checkpointer continuous flushing |
| Date: | 2015-06-02 09:43:06 |
| Message-ID: | 556D7AAA.7020800@lab.ntt.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi Fabien,
On 2015-06-01 PM 08:40, Fabien COELHO wrote:
>
> Turning "checkpoint_flush_to_disk = on" reduces significantly the number
> of late transactions. These late transactions are not uniformly distributed,
> but are rather clustered around times when pg is stalled, i.e. more or less
> unresponsive.
>
> bgwriter_flush_to_disk does not seem to have a significant impact on these
> tests, maybe because pg shared_buffers size is much larger than the database,
> so the bgwriter is seldom active.
>
Not that the GUC naming is the most pressing issue here, but do you think
"*_flush_on_write" describes what the patch does?
Thanks,
Amit
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Kirkwood | 2015-06-02 09:45:25 | Re: pg_xlog -> pg_xjournal? |
| Previous Message | Michael Paquier | 2015-06-02 07:19:40 | Re: [GENERAL] psql weird behaviour with charset encodings |