| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Noah Misch <noah(at)leadboat(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Raising the checkpoint_timeout limit |
| Date: | 2016-02-03 21:07:12 |
| Message-ID: | 56B26C00.5010903@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2/2/16 10:10 PM, Robert Haas wrote:
> Now, you could also set such configuration settings in
> a situation where it will not work out well. But that is true of most
> configuration settings.
Yeah, if we're going to start playing parent then I think the first
thing to do is remove the fsync GUC. The AWS team has done testing that
shows it to be worthless from a performance standpoint now that we have
synchronous commit, and it's an extremely large foot-bazooka to have
laying around.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2016-02-03 21:10:08 | Re: Idle In Transaction Session Timeout, revived |
| Previous Message | Jim Nasby | 2016-02-03 21:01:33 | Re: PostgreSQL Audit Extension |