Skip site navigation (1) Skip section navigation (2)


From: Matthew Wakeling <matthew(at)flymine(dot)org>
To: Greg Smith <greg(at)2ndquadrant(dot)com>
Cc: Laszlo Nagy <gandalf(at)shopzeus(dot)com>, pgsql-performance <pgsql-performance(at)postgresql(dot)org>
Subject: Re: SSD + RAID
Date: 2009-12-08 14:22:17
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-performance
On Fri, 13 Nov 2009, Greg Smith wrote:
> In order for a drive to work reliably for database use such as for 
> PostgreSQL, it cannot have a volatile write cache.  You either need a write 
> cache with a battery backup (and a UPS doesn't count), or to turn the cache 
> off.  The SSD performance figures you've been looking at are with the drive's 
> write cache turned on, which means they're completely fictitious and 
> exaggerated upwards for your purposes.  In the real world, that will result 
> in database corruption after a crash one day.

Seagate are claiming to be on the ball with this one.


 The third years are wandering about all worried at the moment because they
 have to hand in their final projects. Please be sympathetic to them, say
 things like "ha-ha-ha", but in a sympathetic tone of voice 
                                        -- Computer Science Lecturer

In response to


pgsql-performance by date

Next:From: niraj patelDate: 2009-12-08 14:27:35
Subject: Re: Optimizing Bitmap Heap Scan.
Previous:From: Matthew WakelingDate: 2009-12-08 14:03:38
Subject: Re: Optimizing Bitmap Heap Scan.

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group