From: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Enrique Arizón <e_arizon_benito(at)yahoo(dot)com>, pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Advice request: Postgresql setup for flash memories. |
Date: | 2006-08-28 15:59:39 |
Message-ID: | 1156780779.10490.3.camel@state.g2switchworks.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Sun, 2006-08-27 at 16:45, Tom Lane wrote:
> =?iso-8859-1?q?Enrique=20Ariz=F3n?= <e_arizon_benito(at)yahoo(dot)com> writes:
> > since flash memory hardware is dropping prices at
> > high rate I was planning to test how Postgresql runs
> > in such hardware.
>
> This is probably a bad idea, unless the number-of-write-cycles
> limitation of flash memory has gone away while I wasn't looking.
> PG is pretty piggy as far as rewriting disk pages goes, especially
> for the WAL files.
Note that most flash memory controllers randomize the accesses across
the media to prevent / slow this problem. So, it's critical that IF one
has a pg store on a flash device that it have a controller that spreads
writes around. Without that, your flash memory will fail fairly soon.
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Galla | 2006-08-28 22:25:02 | Help about types please |
Previous Message | Gera Mel Handumon | 2006-08-28 06:21:09 | duplicate records after restore |