Re: improving write performance for logging

From: Tom Lane
Subject: Re: improving write performance for logging
Date: ,
Msg-id: 22489.1136579266@sss.pgh.pa.us
(view: Whole thread, Raw)
In response to: Re: improving write performance for logging  (Ian Westmacott)
List: pgsql-performance

Tree view

improving write performance for logging application  (Steve Eckmann, )
 Re: improving write performance for logging application  (Tom Lane, )
  Re: improving write performance for logging application  (dlang, )
   Re: improving write performance for logging application  (Steve Eckmann, )
  Re: improving write performance for logging application  (Steve Eckmann, )
   Re: improving write performance for logging application  (Tom Lane, )
    Re: improving write performance for logging application  (Steve Eckmann, )
 Re: improving write performance for logging application  ("Steinar H. Gunderson", )
  Re: improving write performance for logging application  (Steve Eckmann, )
   Re: improving write performance for logging application  (Kelly Burkhart, )
    Re: improving write performance for logging application  (Steve Eckmann, )
 Re: improving write performance for logging application  (Ian Westmacott, )
  Re: improving write performance for logging application  (Steve Eckmann, )
  Re: improving write performance for logging  (Ron, )
   Re: improving write performance for logging  (Ian Westmacott, )
    Re: improving write performance for logging  ("Jim C. Nasby", )
     Re: improving write performance for logging  (Ian Westmacott, )
      Re: improving write performance for logging  ("Jim C. Nasby", )
       Re: improving write performance for logging  (Ian Westmacott, )
        Re: improving write performance for logging  (Tom Lane, )
      Re: improving write performance for logging  (Michael Stone, )

Ian Westmacott <> writes:
> If the WAL is lost, can you lose more than the data since the last
> checkpoint?

The problem is that you might have partially-applied actions since the
last checkpoint, rendering your database inconsistent; then *all* the
data is suspect if not actually corrupt.

            regards, tom lane


pgsql-performance by date:

From: David Lang
Date:
Subject: Re: help tuning queries on large database
From: Michael Stone
Date:
Subject: Re: improving write performance for logging