| From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
|---|---|
| To: | Julien Cigar <jcigar(at)ulb(dot)ac(dot)be> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Postgres becoming slow, only full vacuum fixes it |
| Date: | 2012-09-24 13:34:31 |
| Message-ID: | 201209241534.31974.andres@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Monday, September 24, 2012 02:53:59 PM Julien Cigar wrote:
> On 09/24/2012 14:34, Andres Freund wrote:
> > On Monday, September 24, 2012 02:21:09 PM Julien Cigar wrote:
> >> 5) synchronous_commit = off should only be used if you have a
> >> battery-backed write cache.
> >
> > Huh? Are you possibly confusing this with full_page_writes?
>
> indeed...! sorry for that
> (note that you still have a (very) small chance of loosing data with
> synchronous_commit = off if your server crashes between two "commit
> chunks")
Sure, you have a chance of loosing the last some transactions, but you won't
corrupt anything. Thats the entire point of the setting ;)
Greetings,
Andres
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kiriakos Tsourapas | 2012-09-24 13:51:44 | Re: Postgres becoming slow, only full vacuum fixes it |
| Previous Message | Julien Cigar | 2012-09-24 12:53:59 | Re: Postgres becoming slow, only full vacuum fixes it |