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

Re: per-tablespace random_page_cost/seq_page_cost

From: Greg Stark <gsstark(at)mit(dot)edu>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: 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:35:24
Message-ID: 407d949e0910261635p68e62de3oacd0b6b45b3b15a1@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Mon, Oct 26, 2009 at 3:05 PM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
> I'm thinking an array, in case we want to make other tablespace cost
> parameters in the future.*  Or, better, whatever structure we're
> currently using for ROLEs.
>
> (* for example, if someone does manage a filesystem with a separate
> cache space per mount, then we'd want effective_cache_size to be
> tablespace-based as well)

Still far from convinced on that one. But effective_io_concurrency
should be included even in the first pass.


-- 
greg

In response to

Responses

pgsql-hackers by date

Next:From: Greg StarkDate: 2009-10-26 23:41:02
Subject: Re: Parsing config files in a directory
Previous:From: Roger LeighDate: 2009-10-26 23:33:40
Subject: Re: Unicode UTF-8 table formatting for psql text output

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