> The first is to add a parameter to CREATE TABLESPACE and ALTER TABLESPACE
> called RANDOMPAGECOST (or something like that) which allows users to set
> the random page cost for a given tablespace. I'm undecided as to whether
> they should be able to set the sequential scan cost. That seems
> reasonable too at first look.
>
> The second option is to have a pg_tablespace.conf file which defines
> tablespace specific settings in some way or another.
>
> Either way, the data will be feed into the planner so that the costing
> routines will be able to use them.
>
> Anyone else got some thoughts on how we could do this in a cleaner manner?
Yes, exactly like we have ALTER USER SET blah=foo; and ALTER DATABASE
SET blah = foo;
Chris
