| From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
|---|---|
| To: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: confusing checkpoint_flush_after / bgwriter_flush_after |
| Date: | 2016-11-25 21:37:16 |
| Message-ID: | alpine.DEB.2.20.1611252232100.29326@lancre |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>> What we do in some similar cases is put the burden on initdb to fill in
>> the correct value by modifying postgresql.conf.sample appropriately.
>> It seems like that could be done easily here too. And it'd be a
>> back-patchable fix.
>
> I haven't realized initdb can do that. I agree that would be the best
> solution.
Indeed.
Maybe something like the following, or maybe it should include "bufmgr.h",
not sure.
--
Fabien.
| Attachment | Content-Type | Size |
|---|---|---|
| dbinit-flush-1.patch | text/x-diff | 946 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-11-25 23:39:13 | Re: confusing checkpoint_flush_after / bgwriter_flush_after |
| Previous Message | Tom Lane | 2016-11-25 21:34:39 | Re: [sqlsmith] Failed assertion in parallel worker in ExecInitSubPlan |