pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Greg Smith <greg@2ndquadrant.com>
To: Scott Marlowe <scott.marlowe@gmail.com>
Cc: Kevin Grittner <Kevin.Grittner@wicourts.gov>
Cc: Craig James <craig_james@emolecules.com>
Cc: Matthew Wakeling <matthew@flymine.org>
Cc: pgsql-performance@postgresql.org
Subject: Re: Weird XFS WAL problem
Date: Thu, 03 Jun 2010 15:31:22 -0400
Message-ID: <4C08030A.20801@2ndquadrant.com> (raw)
In-Reply-To: <AANLkTimBauZ7cZ5Ba78-a9KsaBO418xGJHFT0vGidK8A@mail.gmail.com>
References: <AANLkTikS_QvlkYfv5_hbsXFH4SsTh1nP_WoTwRqpUUcz@mail.gmail.com>
	<AANLkTikegoyBvJXhqZGLZyTwRVyBs4qCuCQ7d1Vntk4w@mail.gmail.com>
	<AANLkTikjkEvj2hG-D1CMu49PQXXbxHVzpXm9JbLWzMQo@mail.gmail.com>
	<AANLkTimtdk11hrWd-OpvXGLrh-4pukGd9eHEUemEM3OR@mail.gmail.com>
	<AANLkTinAhrwwwQKh6NrX-nnvcpxT1EFFlZrUxhaDB87C@mail.gmail.com>
	<AANLkTinuOUTbuke9FTMtwSObcZBio0uOS1ysWrqFyK3t@mail.gmail.com>
	<4C06E994.2080905@emolecules.com>
	<4C06EC01.3060506@catalyst.net.nz>
	<4C07E103.9020909@emolecules.com>
	<alpine.DEB.2.00.1006031811340.4083@aragorn.flymine.org>
	<4C07A0830200002500031E74@gw.wicourts.gov>
	<4C07F1FA.8010909@2ndquadrant.com>
	<4C07B0D30200002500031EAA@gw.wicourts.gov>
	<AANLkTimBauZ7cZ5Ba78-a9KsaBO418xGJHFT0vGidK8A@mail.gmail.com>

Scott Marlowe wrote:
> I think it's a case of the quickest, simplest answer to semi-new tech.
>  Not sure what to do with barriers?  Just flush the whole cache.
>   

Well, that really is the only useful thing you can do with regular SATA 
drives; the ATA command set isn't any finer grained than that in a way 
that's useful for this context.  And it's also quite reasonable for a 
RAID controller to respond to that "flush the whole cache" call by 
flushing its cache.  So it's not just the simplest first answer, I 
believe it's the only answer until a better ATA command set becomes 
available.

I think this can only be resolved usefully for all of us at the RAID 
firmware level.  If the controller had some logic that said "it's OK to 
not flush the cache when that call comes in if my battery is working 
fine", that would make this whole problem go away.  I don't expect it's 
possible to work around the exact set of concerns Kevin listed any other 
way, because as he pointed out the right thing to do is very dependent 
on the battery health, which the OS also doesn't know (again, would 
require some new command set verbage).

-- 
Greg Smith  2ndQuadrant US  Baltimore, MD
PostgreSQL Training, Services and Support
greg@2ndQuadrant.com   www.2ndQuadrant.us




view thread (25+ messages)  latest in thread

Message-ID: <4C08030A.20801@2ndquadrant.com>
Permalink:  ../4C08030A.20801@2ndquadrant.com/
Also on:    postgresql.org/message-id/4C08030A.20801@2ndquadrant.com

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: greg@2ndquadrant.com, scott.marlowe@gmail.com, Kevin.Grittner@wicourts.gov, craig_james@emolecules.com, matthew@flymine.org
  Subject: Re: Weird XFS WAL problem
  In-Reply-To: <4C08030A.20801@2ndquadrant.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox