Re: [GENERAL] pros/cons of using "synchronous commit=off" - AWS in particular

2014-06-20 Thread Alvaro Herrera
Larry Prikockis wrote: > ok... so maybe a better question would be: other than cases of power > failure or something else that caused the server to shut down > unexpectedly and uncleanly, what is the actual risk of data loss? In > my case, the possibility of losing a recent transaction or two in >

Re: [GENERAL] pros/cons of using "synchronous commit=off" - AWS in particular

2014-06-20 Thread Merlin Moncure
On Fri, Jun 20, 2014 at 8:49 AM, Larry Prikockis wrote: > > On 06/20/2014 09:41 AM, Merlin Moncure wrote: >> >> On Thu, Jun 19, 2014 at 9:24 AM, Larry J Prikockis >> wrote: >>> >>> so from the much-loved >>> https://wiki.postgresql.org/wiki/Tuning_Your_PostgreSQL_Server page, we >>> have >>> this

Re: [GENERAL] pros/cons of using "synchronous commit=off" - AWS in particular

2014-06-20 Thread Larry Prikockis
On 06/20/2014 09:41 AM, Merlin Moncure wrote: On Thu, Jun 19, 2014 at 9:24 AM, Larry J Prikockis wrote: so from the much-loved https://wiki.postgresql.org/wiki/Tuning_Your_PostgreSQL_Server page, we have this: " PostgreSQL can only safely use a write cache if it has a battery backup. See WAL

Re: [GENERAL] pros/cons of using "synchronous commit=off" - AWS in particular

2014-06-20 Thread Merlin Moncure
On Thu, Jun 19, 2014 at 9:24 AM, Larry J Prikockis wrote: > so from the much-loved > https://wiki.postgresql.org/wiki/Tuning_Your_PostgreSQL_Server page, we have > this: > > " > PostgreSQL can only safely use a write cache if it has a battery backup. See > WAL reliability for an essential introduc

[GENERAL] pros/cons of using "synchronous commit=off" - AWS in particular

2014-06-19 Thread Larry J Prikockis
so from the much-loved https://wiki.postgresql.org/wiki/Tuning_Your_PostgreSQL_Server page, we have this: " PostgreSQL can only safely use a write cache if it has a battery backup. See WAL reliability for an essential introduction to this topic. No, really; go read that right now, it's vital