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

From Euler Taveira de Oliveira
Subject Re: per-tablespace random_page_cost/seq_page_cost
Date
Msg-id 4AE70EE7.10609@timbira.com
Whole thread Raw
In response to Re: per-tablespace random_page_cost/seq_page_cost  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-hackers
Alvaro Herrera escreveu:
> 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.
> 
+1. That's what I have in mind too.


--  Euler Taveira de Oliveira http://www.timbira.com/


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: FOR UPDATE versus WITH --- change 8.4 too?
Next
From: Tom Lane
Date:
Subject: Re: Endgame for all those SELECT FOR UPDATE changes: fix plan node order