Simon Riggs <[EMAIL PROTECTED]> writes: > On Mon, 2008-09-22 at 16:46 +0100, Gregory Stark wrote: > >> Simon Riggs <[EMAIL PROTECTED]> writes: >> >> > I'd prefer to set this as a tablespace level storage parameter. >> >> Sounds, like a good idea, except... what's a tablespace level storage >> parameter? > > A storage parameter, just at tablespace level. > > WITH (storage_parameter = value)
I still think this is a good idea but I still think there are unanswered questions about it. Surely whatever we do with this parameter also holds for random_page_cost and sequential_page_cost as well? Should they remain GUC parameters at all? If so, how would setting any of them locally interact with the tablespace parameter for tables used in the query? -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's 24x7 Postgres support! -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
