On Wed, Aug 24, 2011 at 2:32 PM, Tomas Vondra <t...@fuzzy.cz> wrote: > On 24 Srpen 2011, 20:48, gnuo...@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).
Well, it's a fair point that TRIM support is probably more widespread on windows. merlin -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
