From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | 赖文豫 <xiaolai913(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: By now, why PostgreSQL 9.2 don't support SSDs? |
Date: | 2013-03-30 16:28:54 |
Message-ID: | 27392.1364660934@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Bruce Momjian <bruce(at)momjian(dot)us> writes:
> On Sat, Mar 30, 2013 at 10:08:44PM +0800, wrote:
>> As we know, SSDs are widely used in various kinds of applications. But the SMGR
>> in PostgreSQL still only
>> support magnetic disk. How do we make full use of SSDs to improve the
>> performance of PostgreSQL?
> When the storage manager (SMGR) says magnetic disk, it is talking about
> read/write media with random access capabillity, vs. something like
> write-only media, which was originally supported in the code. Postgres
> works just fine with SSDs; the only adjustment you might want to make
> is to reduce random_page_cost.
To enlarge on that point: the current smgr layer is basically vestigial,
because the sorts of device dependencies the Berkeley guys envisioned
switching between are nowadays always handled at the filesystem and
kernel device driver layers. md.c is really an interface to the Unix
block device APIs; it has nothing whatsoever to do with whether the bits
are stored on spinning rust or something else.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2013-03-30 16:40:38 | Re: By now, why PostgreSQL 9.2 don't support SSDs? |
Previous Message | Alexander Korotkov | 2013-03-30 16:06:33 | Re: Cube extension improvement, GSoC |