pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tomas Vondra <tv@fuzzy.cz>
To: gnuoytr@rcn.com
Cc: pgsql-performance@postgresql.org
Subject: Re: Reports from SSD purgatory
Date: Wed, 24 Aug 2011 21:32:16 +0200
Message-ID: <d32d411b09d8e7c614772de567a94229.squirrel@sq.gransy.com> (raw)
In-Reply-To: <201108241848.061232@ms14.lnh.mail.rcn.net>
References: <4E49B0A0.2060705@2ndQuadrant.com>
	<201108241848.061232@ms14.lnh.mail.rcn.net>

On 24 Srpen 2011, 20:48, gnuoytr@rcn.com wrote:

> It's worth knowing exactly what that means.  Turns out that NAND quality
> is price specific.  There's gooduns and baduns.  Is this a failure in the
> controller(s) or the NAND?

Why is that important? It's simply a failure of electronics and it has
nothing to do with the wear limits. It simply fails without prior warning
from the SMART.

> Also, given that PG is *nix centric and support for TRIM is win centric,
> having that makes a big difference in performance.

Windows specific? What do you mean? TRIM is a low-level way to tell the
drive 'this block is empty and may be used for something else' - it's just
another command sent to the drive. It has to be supported by the
filesystem, though (e.g. ext4/btrfs support it).

Tomas




view thread (13+ messages)  latest in thread

Message-ID: <d32d411b09d8e7c614772de567a94229.squirrel@sq.gransy.com>
Permalink:  ../d32d411b09d8e7c614772de567a94229.squirrel@sq.gransy.com/
Also on:    postgresql.org/message-id/d32d411b09d8e7c614772de567a94229.squirrel@sq.gransy.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: tv@fuzzy.cz, gnuoytr@rcn.com
  Subject: Re: Reports from SSD purgatory
  In-Reply-To: <d32d411b09d8e7c614772de567a94229.squirrel@sq.gransy.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