Re: per-tablespace random_page_cost/seq_page_cost - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: per-tablespace random_page_cost/seq_page_cost
Date
Msg-id 20091026235253.GO8812@alvh.no-ip.org
Whole thread Raw
In response to Re: per-tablespace random_page_cost/seq_page_cost  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: per-tablespace random_page_cost/seq_page_cost
List pgsql-hackers
Tom Lane escribió:
> Greg Stark <gsstark@mit.edu> writes:
> > Still far from convinced on that one. But effective_io_concurrency
> > should be included even in the first pass.
> 
> I think a design that is limited to a prespecified set of GUCs is
> broken by definition.  It'd be better to make it work like
> ALTER DATABASE SET.

Well, not exactly like ALTER DATABASE SET because those are now stored
in pg_db_role_setting.  But a new spcoptions column storing an array of
key/value pairs seems a reasonable way to do it.

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.


pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: per-tablespace random_page_cost/seq_page_cost
Next
From: Itagaki Takahiro
Date:
Subject: Re: "toast.fillfactor" is documented but not recognized?