Postgres Pro
Downloads
Home   >   mailing lists

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

From Tom Lane
Subject Re: per-tablespace random_page_cost/seq_page_cost
Date
Msg-id 17410.1256600559@sss.pgh.pa.us
Whole thread Raw
In response to Re: per-tablespace random_page_cost/seq_page_cost  (Greg Stark <gsstark@mit.edu>)
Responses Re: per-tablespace random_page_cost/seq_page_cost
Re: per-tablespace random_page_cost/seq_page_cost
List pgsql-hackers
Tree view 
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.
        regards, tom lane

pgsql-hackers by date:

Previous
From: Greg Stark
Date:
Subject: Re: Parsing config files in a directory
Next
From: Andres Freund
Date:
Subject: Re: per-tablespace random_page_cost/seq_page_cost