| From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
|---|---|
| To: | sthomas(at)optionshouse(dot)com |
| Cc: | "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Tablespace-derived stats? |
| Date: | 2012-10-19 15:05:10 |
| Message-ID: | CAMkU=1zz5_rRfWokMjTCsxGR1Q-W=5ZAK+_Vj=mryXBnRD7RQw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Fri, Oct 19, 2012 at 7:29 AM, Shaun Thomas <sthomas(at)optionshouse(dot)com> wrote:
> Hello Perf,
>
> Lately I've been pondering. As systems get more complex, it's not uncommon
> for tiered storage to enter the picture. Say for instance, a user has some
> really fast tables on a NVRAM-based device, and slower-access stuff on a
> RAID, even slower stuff on an EDB, and variants like local disk or a RAM
> drive.
>
> Yet there's only one global setting for random_page_cost, and seq_page_cost,
> and so on.
>
> Would there be any benefit at all to adding these as parameters to the
> tablespaces themselves?
Been done already:
http://www.postgresql.org/docs/9.0/static/sql-altertablespace.html
Cheers,
Jeff
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Shaun Thomas | 2012-10-19 15:07:03 | Re: Tablespace-derived stats? |
| Previous Message | Claudio Freire | 2012-10-19 15:02:49 | Re: How to upgrade from 9.1 to 9.2 with replication? |