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: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)postgresql(dot)org, Josh Berkus <josh(at)agliodbs(dot)com>
Subject: Re: per-tablespace random_page_cost/seq_page_cost
Date: 2009-11-01 12:43:57
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On Sat, Oct 31, 2009 at 6:04 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> Looking at this a little more, it seems that part of the motivation
> for the existing design is that user-created AMs might require
> arbitrary options, which therefore can't be wired into the system
> catalogs.  There's no equivalent for tablespaces (we could add one
> some day, I suppose), so there's less intrinsic reason to think we
> have to do it that way.

Can't custom modules define arbitrary options which they declare can
be defined per tablespace?

We could have a column for all booleans, a column for all integers,
etc. but that's not really any more normalized than having a single
column for all the types with a rule for how to marshal each value


In response to


pgsql-hackers by date

Next:From: Robert HaasDate: 2009-11-01 15:02:18
Subject: Re: per-tablespace random_page_cost/seq_page_cost
Previous:From: Hitoshi HaradaDate: 2009-11-01 05:42:19
Subject: Re: half OOT, plv8js group created ^^

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