Skip site navigation (1) Skip section navigation (2)

Re: per-tablespace random_page_cost/seq_page_cost

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Greg Stark <gsstark(at)mit(dot)edu>
Cc: Josh Berkus <josh(at)agliodbs(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: per-tablespace random_page_cost/seq_page_cost
Date: 2009-10-26 23:42:39
Message-ID: 17410.1256600559@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Greg Stark <gsstark(at)mit(dot)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

In response to

Responses

pgsql-hackers by date

Next:From: Andres FreundDate: 2009-10-26 23:47:56
Subject: Re: per-tablespace random_page_cost/seq_page_cost
Previous:From: Greg StarkDate: 2009-10-26 23:41:02
Subject: Re: Parsing config files in a directory

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group