| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Noah Misch <noah(at)leadboat(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Ashutosh Sharma <ashu(dot)coek88(at)gmail(dot)com>, Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, Mithun Cy <mithun(dot)cy(at)enterprisedb(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Subject: | Re: Perf Benchmarking and regression. |
| Date: | 2016-06-04 00:43:12 |
| Message-ID: | 20160604004312.ibwcsobu7eapimen@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2016-06-03 20:41:33 -0400, Noah Misch wrote:
> Disabling just backend_flush_after by default works for me, so let's do that.
> Though I would not elect, on behalf of PostgreSQL, the risk of enabling
> {bgwriter,checkpoint,wal_writer}_flush_after by default, a reasonable person
> may choose to do so. I doubt the community could acquire the data necessary
> to ascertain which choice has more utility.
Note that wal_writer_flush_after was essentially already enabled before,
just a lot more *aggressively*.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christophe Pettus | 2016-06-04 02:10:44 | HashAggregate row estimate = 200 |
| Previous Message | Noah Misch | 2016-06-04 00:41:33 | Re: Perf Benchmarking and regression. |