On 10/10/2012 09:49 AM, Strahinja Kustudić wrote:
I will change those, but I don't think this is that big of an issue if most of the IO is done by Postgres, since Postgres has it's own mechanism to tell the OS to sync the data to disk. For example when it's writing a wal file, or when it's writing a check point, those do not get cached.
You'd be surprised. Greg Smith did a bunch of work a couple years back that supported these changes. Most DBAs with heavily utilized systems could even see this in action by turning on checkpoint logging, and there's an occasional period where the sync time lags into the minutes due to a synchronous IO switch. -- Shaun Thomas OptionsHouse | 141 W. Jackson Blvd. | Suite 500 | Chicago IL, 60604 312-444-8534 sthomas@xxxxxxxxxxxxxxxx ______________________________________________ See http://www.peak6.com/email_disclaimer/ for terms and conditions related to this email -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
