On Fri, Oct 19, 2012 at 7:29 AM, Shaun Thomas <sthomas@xxxxxxxxxxxxxxxx> 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 -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
